Scripts can be triggered in different places and by different events. The following list indicates the configuration files in which scripts can be referenced, the events upon which the scripts can be triggered, and the actual scripts that can be triggered on each of these files.
|For more information about the variables available to scripts, refer to Script variables.|
- Scripts called in mappings
- Triggered by situation
onCreate, onUpdate, onDelete, onLink, onUnlink
- Object filter
- Triggered when correlating objects
- Triggered on any reconciliation
- Scripts inside properties
Mappings support one script per hook. If multiple scripts are defined for the same hook, only the last one is kept.
- Scripts inside policies
Within a synchronization policy, you can use a
conditionscript to apply different policies based on the link type, for example:
- Scripts called in the managed object configuration
onCreate, onRead, onUpdate, onDelete, onValidate, onRetrieve, onStore, onSync, postCreate, postUpdate, and postDelete
The managed object configuration supports only one script per hook. If multiple scripts are defined for the same hook, only the last one is kept.
- Scripts called in the router configuration
onRequest, onResponse, onFailure
The router configuration supports multiple scripts per hook.