The schema used in the examples for the sales order business object is shown next:
SalesOrderClass { SOHeader { int SalesOrderNo; BSTR SalesPersonName; BSTR SalesOrganizationName; float CommitionAmount; } SOLineItems1 { int SerialNumber; BSTR ItemName; float QTY; float Discount; } SOLineItems2 { int SerialNumber; BSTR ItemName; float QTY; float Discount; } SOLineItems3 { int SerialNumber; BSTR ItemName; float QTY; float Discount; } SOLineItems4 { int SerialNumber; BSTR ItemName; float QTY; float Discount; } }
The get
operation demonstrates a Request-Response scenario.
To retrieve a sales order record:
Sales Order
.Get
. The Get SO Details page is displayed. SO Number
field or use the default.ENTRY NOT FOUND
is displayed on the html page.
The Insert-Update
operation demonstrates a Request-Response scenario.
To insert or update a sales order record:
Sales Order
.Insert-Update
. The Sales Order Insert_Update page is displayed. Sales Order Number
field or use the default.INSERTED ENTRY
, is displayed on the html page. If the record exists, it is updated and the status UPDATED ENTRY
is displayed on the html page.
The delete
operation demonstrates a Request-Response scenario.
To delete a sales order record:
Sales Order
.Delete
. The Delete SO Details page is displayed. SO Number
field or use the default.DELETED ENTRY
is displayed on the html page. If the sales order record does not exist, the status ENTRY NOT FOUND
is displayed on the html page.
The Sync
operation demonstrates a Publication scenario. TIBCO BusinessWorks listens to the publish events related to the sales order business object, and displays this information on the browser when you use the Sync
operation.
The Sync
operation is only available for the TIBCO BusinessWorks examples.
To publish a sales order record:
TIBCO Adapter™ for COM Examples Guide Software Release 5.3, September 2005 Copyright © TIBCO Software Inc. All rights reserved www.tibco.com |