Compliance Engine

Apps use a Compliance Engine to provide backend shipping capability (Logistics Server). Compliance Engine is a property of the Transtream instance defined during installation, but you can change it. See Change Compliance Engine for details. Once installed, the Compliance Engine is setup and managed using the Administration App (with the exception of adding or updating carrier components which is achieved using Transtream Setup).

Apps integrate with Logistics Server through XML requests. For example, you have XML requests for rate, ship and return. Snippets, such as the Carrier Service snippet, are preconfigured to use and handle the XML requests necessary for their purpose, and the snippet's Properties will expose necessary or optional configuration. In addition, Button controls can have an Action of XML Request. Once you select the XML request triggered by the button, Designer lets you map it to the controls in your App that will construct the content required in the request.

Typically, Apps are Compliance Engine agnostic. You can develop or modify Apps secure in the knowledge that they will work regardless of the Compliance Engine being used. This makes Apps highly portable and reusable. Apps are stored in single XML files. To move them between instances, simply import them in Product Admin.

Article last edited 11 February 2019