Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

Modifying Custom Triggers to Use Objects as Process Objects, Step Objects, or Both

Add code to existing custom triggers to use objects as process objects, step objects, or both.

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 to create each one manually 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.

Now, administrators can add a 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

  1. Go to Salesforce Setup.
  2. Go to the desired object using the Quick Find Search Box or the Object Manager.
  3. Click Triggers.
  4. Click the custom trigger created for Conga Orchestrate. Example: Custom_ObjectStepTrigger
  5. Click Edit.
  6. 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();
  7. Click Save.

    See the example below for correct trigger syntax.

    Note: Orchestrate requires that the following trigger hooks be present in the modified Apex trigger:
    before insert, after insert, before update, after update, before delete, after delete, after undelete