| #Trigger Events |
Do Not Track AGG Sources in Trigger? | When enabled, DSP will not trigger the aggregation calculations while the aggregated source data is being modified. This is particularly useful when bulk changes to the aggregated source data are initiated by integrations or batch jobs, allowing the calculations to delay and resume separately once the bulk data changes are complete, by performing blank updates to the impacted aggregation target records in a separate batch job. |
Before Insert Trigger? | When enabled, the Executable runs on the Before Insert event, using the records in the 'Trigger.new' context as its input. |
After Insert Trigger? | When enabled, the Executable runs on the After Insert event, using the records in the 'Trigger.new' context as its input. |
Before Update Trigger? | When enabled, the Executable runs on the Before Update event, using the records in the 'Trigger.new' context as its input. |
After Update Trigger? | When enabled, the Executable runs on the After Update event, using the records in the 'Trigger.new' context as its input. |
Before Delete Trigger? | When enabled, the Executable runs on the Before Delete event, using the records in the 'Trigger.old' context as its input. |
After Delete Trigger? | When enabled, the Executable runs on the After Delete event, using the records in the 'Trigger.old' context as its input. |
After Undelete Trigger? | When enabled, the Executable runs on the After Undelete event, using the records in the 'Trigger.new' context as its input. |
| Order of Execution, Permissions, and More |
Pipeline | The Pipeline this Executable belongs to. Pipelines group related Executables so you can navigate, filter, and reorder them together. Within a Pipeline, Executables run in the order set by their sequence number. |
Seq No. | Sequence number of this Executable within its Pipeline, determining the order of batch executions, triggers, data lists, and action buttons. |
Applicable for Self-Adaptive Trigger? | Executables where the source and target objects are the same, the Action is "Update" or "Upsert", and have a one-to-one match through the "Id" field, are considered Applicable for Self-Adaptive Trigger. A Self-Adaptive Trigger operates on the same record being processed, dynamically adapting to its own field values for in-memory transformations or validations, with no DML committed. |
Applicable for Trigger Action? | Indicates that this Executable is a Trigger Action (not Self-Adaptive). Trigger Action performs DML on target records; Self-Adaptive applies field transformations/validations in memory without committing DML. |
All Internal Users Have Read Access? | When enabled, DSP creates a sharing record granting all internal users read access to the current Executable; this field is automatically turned on when #Trigger, #Data List, or #Action Button is enabled and can be disabled manually to revoke that access. |
Run Once on Recursive Updates? | When enabled, the trigger logic defined in the Executable will be executed only once when recursive updates occur, preventing multiple executions for a single trigger event. Note: If the Executable is enabled for both Before Update and After Update, and both events trigger the execution, it will not be considered recursion, and the logic will be executed twice. |
Access Permissions | Comma separated custom permission names. If set, access is restricted to users who possess at least one of the listed permissions. |
Bypass Triggers Custom Permissions | Comma separated custom permission names. If set, users with any of the custom permissions will bypass the trigger execution. |
