Pattern: Derive Dependent Data Before Saving

In contrast to the Derive dependent data immediately after modification pattern, Business Object Processing Framework (BOPF) evaluates all changes made so far in the current transaction to check the trigger condition.

The trigger condition of a determination configured according to this pattern is checked as soon as the consumer saves the whole transaction. If the transaction cannot be saved, determinations of this pattern can run multiple times.

Since this evaluation takes place only during the save phase of the transaction, the Derive dependent data before saving pattern is recommended for time consuming determinations.

The data of each invoice must also be stored in an XML file. A determination is configured to extract the XML code from each changed invoice. Since this is very time consuming the determination does not run immediately after each change of an invoice. Instead, it runs once, before being saved, for all invoices changed during the current transaction.