Check delivery instruction combinations

Event action – Abstract

Purpose: Checks whether the combination of the delivery instruction attributes selected for the reference object is permissible against the background of applicable Delivery instruction combinations (matrix), if any.

See also: Delivery instruction, Delivery instruction combinations

images/download/attachments/62850413/image2021-5-14_15-1-42-version-1-modificationdate-1620997305070-api-v2.png

The event action Prüfe die Lieferhinweiskombinationen checks whether the combination of delivery instruction attributes selected for the reference object is permissible against the background of any applicable Delivery instruction combinations (matrix).

If the reference object has at least one pair of two 'non-combinable' delivery instruction attributes, this triggers an error message that causes the event handling to be aborted and, if necessary, also causes a rollback of the transaction.

The error message lists all combinations of delivery instructions that are considered incompatible, based on the applicable matrix of Delivery instruction combinations (see the example below).

Configuration

The business transaction object to be checked must exist as a reference object for the event action.

The event action does not use any parameters.

Example

For a given type of Orders, the following matrix for Delivery instruction combinations is applicable:

images/download/attachments/62850413/image2021-5-14_14-58-6-version-1-modificationdate-1620997089323-api-v2.png

  • Specifically, this means that only two of the three available delivery instructions may be combined, namely 'Same Day Delivery' and 'Notification by driver (...)'.

    • 'Same Day Delivery' and 'Click And Collect' concern an exclusive selection (correspondingly: EITHER delivery OR pickup).

    • In connection with a pickup stated by the delivery instruction 'Click And Collect', the instruction 'Notification by driver (...)' is meaningless.

Technically, the delivery instructions in the input form for purchase orders should initially be able to be freely combined and saved in a Repeatable element container without any restrictions.

The valid combination of delivery instructions should only be checked in the course of the 'release' of a purchase order. The working state 'Released' should only be assigned with a combination of permissible delivery instructions.

Configuration:

To check the delivery instruction combinations for an order 'in the course of release', an event handling is created and configured as shown on the right:

  • The assignment of the 'Released' working state (see Working state (Events) is selected as the Triggering event. This event is triggered when the 'Released' working state is assigned.

  • The Validating rule is intended to use a Typprüfung to ensure that an 'Order' is present as an input value. Further checks (e.g. for the 'Order type') have been omitted here.

  • As an Action on passed rule, only the event action Prüfe die Lieferhinweiskombinationen is required. The output of an error message for the user is implemented implicitly.

NOTE◄ If further checks that issue confirmations are relevant for the release, these should be placed before the event action Prüfe die Lieferhinweiskombinationen, since this reacts to any conflicts by 'error', which causes the immediate cancellation of the event handling (and if necessary a rollback of the transaction).

images/download/attachments/62850413/image2021-5-14_14-59-6-version-1-modificationdate-1620997148842-api-v2.png

Runtime example:

When attempting to assign the working state 'Released' to a purchase order for which all three available delivery instructions are used, the following error message appears:

images/download/attachments/62850413/image2021-5-14_15-0-15-version-1-modificationdate-1620997218246-api-v2.png