Event In Interface

Receive event data data from 3rd parties and process into shipment milestones in Scope

Top features

With the Event In interface, your shippers, consignees, trucker, agents etc. could update shipments with status information directly in Scope. Tracking Templates in Scope could be set up to use inbound event data for updating milestones in Scope automatically.

Prerequisite

A technical data communication channel is required between the Riege data center and the sender of the event data. This channel gets a senderID assigned by Riege. The senderID is required for the setup in Scope.

All Scope branch offices are potential event message receivers and are assigned a receiverID. The receiverID default value is the code of the corresponding partner. The receiverID should also be aligned with Riege for setup in the Riege internal message clearing system.

• The interface cannot send updates nor cancellations.
• The description of the Scope Events Message Format is available at
  https://riege.github.io/xml-event

Technical information

• Event data can also include documents , e.g. a picture of a proof of delivery document/signature.
• To send the data, a transmission path (e.g. Riege Software SFTP) must be defined and configured with the recipient of the data.

Scope Setup - Tracking Templates

Scope could complete milestones in tracking templates based upon processed event data.

A milestone is automatically completed when event data is processed in Scope matching an entry in Tracking Templates > Milestone Templates > General > Triggering Events.

For more information about tracking templates, see Tracking Templates and Tracking Plans