Event Reason Codes created using the Event Reason Codes function from the System Settings module can be configured for various uses via the Event Associations function also from the System Settings module. Transportation Manager provides a set of reason codes for all entity status update events and supported user generated events. Users are allowed to add their own reason codes and associate them to various events.
The presentation of the reason codes is based on the configurations in Event Associations. When operations such as Generate Event, Cancel (Load), Reject (Tender), POD are triggered, the application identifies the immediate event for the operation, the status of the entity and the user's user group type, and uses the combination of these criteria to retrieve the available reason codes. These available reason codes will be presented for the user to select. If one the available reason codes is also defined as the UI Default, this reason code will be pre-selected for the user.
In the case of Generate Event operation, if no reason code is available, the operation will not be allowed.
In the case of certain system controlled event, such as Tender Reject or POD, if no reason code is available, system provided one will be the reason code provided for selection even when this very reason code is set to be unavailable in Event Associations.
In the case of some generic operations for entity status update, such as canceling shipments, loads, trips, or status reversal, when there are more than one reason codes available, the Request Reason Code page will be displayed; otherwise, the only available reason code, or a system provided reason code will be used behind the scene, and the Request Reason Code page will be by-passed.
In the case of events indirectly triggered by the user triggered event, the system determines the reason code to use and the Event Associations configurations are ignored. For example, when a user triggers the POD event on the last shipment leg of a shipment, the system automatically triggers the POD for the shipment behind the scene. The configured reason codes for Shipment Leg Proof of Delivery will be considered; but reason code for Shipment Proof of Delivery will be supplied by the system rather than from the configuration for the Shipment Proof of Delivery event.
The reason code will be saved with the applicable entity data for the applicable status transition history, monitoring situations, event notifications and audits.