Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space PRINSAG and version 8.3

The OPS Data Model contains only one event and one action. The Order Submitted event fires when a customer checks out an order from the OPS web site. The action Post Status to OPS is used to post a status to the OPS web site for customer viewing.
The data model includes an XML schema that describes the contents of an order from OPS (that is, a checked-out shopping cart.) It is called OPSOrder and is stored in the General/OPS group in RBA XML Schema Manager, which can be opened from Rule Set Manager.
The schema allows for arbitrary elements to be added to a product when it is being ordered, using an element type called Extrinsic which has arbitrary content. The sample rule OPSProcessUpload shows some examples of processing Extrinsic elements. See Sample rules for more details.
The data model also includes a web service which accepts orders from OPS and passes them to RBA. Each order is saved in a file called Order<timestamp>Cart<cartnumber>.xml in the configured OrderStorage directory.
If there are no rules enabled to accept OPS orders—that is, a System-enabled rule which is triggered by an Order Submitted event, then the web service rejects the order, and OPS will resubmit it later. Rejected orders are kept in the Rejected subdirectory of the configured OrderStorage directory.