Difference between revisions of "Journey Reference"
From Commander4j Wiki
(Created page with "A Journey Reference is optional data which can be added to the despatch header. It is intended to allow the Commander4j application to be linked to an external plannning appli...") |
|||
| Line 4: | Line 4: | ||
A list of Journey References is maintained in a separate table. This table can be updated manually or via an xml message. | A list of Journey References is maintained in a separate table. This table can be updated manually or via an xml message. | ||
| + | |||
| + | [[File:journey_ref1.jpg]] | ||
Revision as of 11:33, 15 June 2016
A Journey Reference is optional data which can be added to the despatch header. It is intended to allow the Commander4j application to be linked to an external plannning application.
When a despatch is being created a field called "Journey Ref" is available on screen where the operator can put in the tracking number provided by the external system. The requirement for this Journey Reference to be entered and validated is determined by a property of the destination location.
A list of Journey References is maintained in a separate table. This table can be updated manually or via an xml message.
