Pattern: Derive Dependent Data Immediately After Modification
This pattern is used to recalculate data after node instances have been created, updated, or deleted.
The trigger condition of a determination of the pattern Derive dependent data immediately after modification is evaluated at the end of each modification. A modification roundtrip is defined as one single modification core service call from the consumer to Business Object Processing Framework (BOPF). The call contains any creation, update, or deletion of node instances. Additionally, the trigger condition is checked after each action core service has been executed.
If there is no need to react immediately on the modification, and the handling of the side effect is very time consuming, we recommend you use the Derive dependent data before saving determination pattern instead.
As soon as a new ITEM node instance of the CUSTOMER_INVOICE business object is added, the changed item amount (price multiplied by quantity) must immediately be recalculated to show the new amount on the consumer’s user interface.