Event entry settings

Make the settings here that affect the behavior of the Event Capture module.

Changed settings must be applied by clicking on the Save button.

ATTENTION: The settings apply system-wide to all workstations and are only applied after a restart of CodX PostOffice takes effect!

Behaviour if the item for which an event is entered is not (yet) stored in PostOffice

In this group you define how CodX PostOffice should behave when an item is scanned that is not yet saved. is not yet saved.

Guided event recording

This is the entry on the PC, where you can see all messages.
The following options are available:

• No check, create empty item if necessary
  No check will be performed and if necessary an empty item will be created in CodX PostOffice.

• Check whether the shipment is stored, ask the operator if necessary.
  It is checked whether this transmission is stored. If this is not the case, the operator is asked how he wants to proceed. he would like to do.

• Check if shipment is saved, warning and do not save shipment.
  The shipment is checked and if no shipment is saved, a warning is issued and the shipment is not saved.

Radio scanner event detection

This mode is used when the items are captured by radio scanner and there is no view of the screen.
The following options are available for selection:

• No check, create empty item if necessary
  No check will be performed and if necessary an empty item will be created in CodX PostOffice.

• Check if shipment is saved, warning and do not save shipment.
  A check is made and a warning signal is output, the transmission is not saved.

Save data synchronously

This setting defines whether the captured event data is stored synchronously (default, checkbox set) or asynchronously. asynchronously.

• Synchronous storage
  The data is stored directly in the database when it is entered and is therefore immediately available for other process steps. available.
  The user interface is only ready for the next recording when the storage is completed.
  If the database is very busy, the data entry can become "sluggish".

• Asynchronous storage
  The data is stored in an intermediate buffer, which is processed in the background.
  The data is only available for other process steps after a delay of several minutes!
  The user interface is not slowed down by the storage/processing.

Inherit delivery events to shipments based on logistics entity (carrier route, depot, ...):

Defines whether logistics entities (carrier route, carrier route group, depot, unloading point, delivery tour, delivery round group, home delivery organization, transshipment point) are allowed as entries.
If this function is activated (checkbox set) the above logistics entities can be entered like a shipment. The delivery event is then inherited by all shipments that are assigned to this entity at the time of entry.
Default value: Yes (switched on)

Acquisition with alternative code:

This setting defines whether shipments can also be entered/referenced via alternative code.

• Entry with alternative code off
  Shipments are generally not entered via alternative code. The corresponding checkbox in the user interface is is switched off and cannot be used.

• Entry with alternative code on
  In general, shipments can always be entered via alternative code. The corresponding checkbox in the user interface is is switched on and cannot be operated.

• Acquisition with alternative code adjustable (default)
  If the corresponding checkbox is selected in the user interface, consignments can be entered via alternative code.