Tracking state history
A chronological list of all Tracking state entries referring to the same owner (statusOwner) – a certain business object or one of its line items (see Working with tracking states) – is called Tracking state/History.
The Tracking state/History of a selected business object can be opened by clicking the button History in the default ribbon of an overview or details view for the business object type (Main category Common, sub category Tracking state):
Clicking the History button opens a modal view for Tracking state entries:
For Orders, Shipments or an Allgemeines Geschäftsobjekt the view appears, as shown above, with an example of an order. For Manifests, the tree view section on the left is omitted, since manifests only feature tracking states at header level.
The default ribbon features the common buttons for managing Details (New, Cancel, Copy, Save) and controlling the List (Clear, Remove).
The Back button closes the modal view for Tracking state/History.
►NOTE◄ The default button Delete does not appear in the details category, as tracking state entries must not be deleted, by definition.
The tree view on the left view resembles all line items and sub line items of the business object (here: Order) down from the header level. A mouse click in this area defines a selection for the 'Owner' element, for which the tracking state history should be reviewed or edited. The selected level ('Order' in screenshot) appears highlighted (background color).
In addition to the header level and the line items identified by automatically assigned line item numbers (here e.g. 'OPO1'), the tree features one 'group node' per Line item type, which contains all line items of that type. Since there are no tracking state entries linked to these virtual elements of the tree, they cannot be selected, but only expanded or reduced.
On the right side of the tree view area a 'details column' Current is visible, where the current value of the tracking state attribute for the default Tracking state type 'Current' is indicated, if available. By default, the two default tracking state types 'Current' and 'Current visible' (see Tracking state type) are indicated here. However, the configuration for the ribbon command (Verfügbare Befehle, Tracking state/History) enabled different choices per context.
The datagrid in the lower section of the view lists Tracking state entries belonging to the 'Owner' selected in the tree view. The example in the screenshot lists two tracking state entries at the header level.
The details area above the list features details of an entry selected in the list for reading and – if allowed – editing or allows input for a New entry to add to the list. The design of the details area depends on the applicable input form for tracking state entries for a given data context (see Association criteria). The screenshot shows the default configuration for this form. Custom configurations (see Tracking state entry forms) may include typed attributes among other options.
►NOTE◄
Changes to the properties Tracking state code and External input for already created tracking state entries are denied with an error prompt, when Save is clicked.
Other properties may be edited for existing entries, unless custom restrictions apply as a result of configurations for input forms, event handling or permissions.
Choices available in Combobox Tracking state code for new entries, depend on the definitions for transformation matrices in applicable Tracking state workflows (if any). Restrictions are applied on the assumption that an additional entry will follow the current status in chronological sequence.
►IMPORTANT◄ Until a new tracking state is created by saving it for the first time, a user may assign an arbitrary External input date/time value, unless the input form restricts access to the element or the range of values. Before saving an entry, the system evaluates the chronological status sequence resulting when the new entry is added to the tracking state history considering selections for Tracking state code and External input date/time. Saving is denied, if Tracking state workflows apply, which do not support the transformation to the added tracking state from the preceding entry in the history. The transformation from the added state to that of a subsequent entry (if any) is not evaluated!