Add additional code to existing custom triggers to use objects as a process objects, step object, or both for Conga Orchestrate.
Use existing Conga Orchestrate triggers to set up and use an object as a Process object, Step object, or both.
Previously, Conga Orchestrate required administrators to deploy new custom triggers in Conga Orchestrate Setup, or manually create each one, to use an object as a Process object, Step object, or both. For example, a custom object set up as a Process object would require an additional custom trigger to use it as both a Step and Process object moving forward.
Now, administrators can simply add an additional line of code to existing triggers to use an object as a Process object, Step object, or both.
Note: Adding this code to the custom triggers only pertains to users with existing triggers.
To modify an existing trigger:
- Navigate to Salesforce Setup.
- Navigate to the desired object using Quick Find Search Box or the Object Manager.
- Click Triggers.
- Click the custom trigger created for Conga Orchestrate. Example: Custom_ObjectStepTrigger
- Click Edit.
- Copy one of the code options below and paste it as a new line of code after all the current logic in the trigger.
- To setup as a Process object, add: FSTR.COTriggerHandler.handleProcessObjectTrigger();
- To setup as a Step object, add: FSTR.COTriggerHandler.handleStepObjectTrigger();
- To setup as both, add: FSTR.COTriggerHandler.handleBothTrigger();
- Click Save.
See the example below for correct trigger syntax.Important: Orchestrate requires that the following trigger hooks are present in the modified Apex Trigger:
before insert, after insert, before update, after update, before delete, after delete, after undelete