With this release, the definition of triggers for data quality rule executions as well as for business process management has been enhanced and simplified. There are 4 major improvements in the UI configuration which lead to better administration and productivity in the setup of the system:
A multi-selection for the parameters to set up a single trigger configuration (e.g. for multiple catalogs in one go):
More data types are available to choose from.
A field selection dialog for the modification fields selection to support a convenient setup without the need to worry about technical syntax definitions.
An active flag for trigger configurations to be able to set them (temporarily) to inactive without the need to drop the whole configuration entirely from the setup of the server.
Besides these enhancements, a completely new trigger type for workflow setups has also been introduced. The new "Entity deleted" trigger event gives, for example, the option to inform third party systems like online stores via a workflow or direct queue communication to trigger corresponding updates.
Additionally, the payload for BPM triggers can be selected. It can be decided if only the meta information should be transferred (user, timestamp, affected fields), or also the old and new value should be included in the payload. This can be leveraged to keep downstream systems in sync with data changes.
Note that the payload format has changed and may require adaptions. Please find further information in the "Trigger Payload" chapter of the configuration manual.