Difference between revisions of "Journey Reference"

From Commander4j Wiki
Jump to: navigation, search
 
Line 8: Line 8:
  
  
The PC desktop version of the Despatch Screen shown below with a pop-up list of available Journey References.
+
'''The PC desktop version of the Despatch Screen shown below with a pop-up list of available Journey References.'''
  
 
[[File:journey_ref2.jpg]]
 
[[File:journey_ref2.jpg]]
  
  
The Scanner web version of the Despatch Screen shown below with a Journey References input field.
+
'''The Scanner web version of the Despatch Screen shown below with a Journey References input field.'''
  
 
[[File:journey_ref3.jpg]]
 
[[File:journey_ref3.jpg]]
  
  
Despatch Documentation with Journey Reference.
+
'''Despatch Documentation with Journey Reference.'''
  
 
[[File:journey_ref4.jpg]]
 
[[File:journey_ref4.jpg]]

Latest revision as of 11:47, 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.

Journey ref1.jpg


The PC desktop version of the Despatch Screen shown below with a pop-up list of available Journey References.

Journey ref2.jpg


The Scanner web version of the Despatch Screen shown below with a Journey References input field.

Journey ref3.jpg


Despatch Documentation with Journey Reference.

Journey ref4.jpg