home

Orchestrate

Adobe Sign ServicesAdvantage Platform AdministrationApprovals for Advantage PlatformApprovals for SalesforceBilling for Advantage PlatformBilling for SalesforceCLM for Advantage PlatformCLM for SalesforceContracts for SalesforceCollaborateComposer for Advantage PlatformComposer for SalesforceContractsConga for Google DocsConga Upgrade ProgramContract Intelligence (Standalone)CPQ for Advantage PlatformCPQ for SalesforceDeal MaximizerDigital Commerce for Advantage PlatformDigital Commerce for SalesforceDiscovery AI for Advantage PlatformDiscovery AI for SalesforceDocusign ServiceseSignature Integration with Advantage PlatformGridInvoice GenerationMix FormsOrchestrateOrder Management for Advantage PlatformOrder Management for SalesforcePartner Commerce for Advantage PlatformPartner Commerce for SalesforceQuote GenerationSign for Advantage PlatformSign for SalesforceSmart SearchTurboEnginesX-Author for Contracts 1.0 (Classic)X-Author for ContractsX-Author for Contracts Advanced for Advantage PlatformX-Author for Contracts Advanced for SalesforceX-Author for ExcelX-Author for Migration ManagerRelease NotesGeneral
Adobe Sign ServicesAdvantage Platform AdministrationApprovals for Advantage PlatformApprovals for SalesforceBilling for Advantage PlatformBilling for SalesforceCLM for Advantage PlatformCLM for SalesforceContracts for SalesforceCollaborateComposer for Advantage PlatformComposer for SalesforceContractsConga for Google DocsConga Upgrade ProgramContract Intelligence (Standalone)CPQ for Advantage PlatformCPQ for SalesforceDeal MaximizerDigital Commerce for Advantage PlatformDigital Commerce for SalesforceDiscovery AI for Advantage PlatformDiscovery AI for SalesforceDocusign ServiceseSignature Integration with Advantage PlatformGridInvoice GenerationMix FormsOrchestrateOrder Management for Advantage PlatformOrder Management for SalesforcePartner Commerce for Advantage PlatformPartner Commerce for SalesforceQuote GenerationSign for Advantage PlatformSign for SalesforceSmart SearchTurboEnginesX-Author for Contracts 1.0 (Classic)X-Author for ContractsX-Author for Contracts Advanced for Advantage PlatformX-Author for Contracts Advanced for SalesforceX-Author for ExcelX-Author for Migration ManagerRelease NotesGeneral

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.

Show Contents

Show Page Sections

Orchestrate

Advanced Setup

download

Creating an Apex Trigger for a Custom Object as a Step

A trigger is Apex code that executes before or after specific data manipulation language (DML) events occur, such as before object records are inserted into the database, or after records have been deleted. A list of all triggers in your organization is located in Setup under Apex Triggers. You can invoke Apex through the use of triggers. Apex triggers are stored as metadata in the application under the object with which they are associated.

A trigger is Apex code that executes before or after the following types of operations:

  • Insert
  • Update
  • Delete
  • Merge
  • Upsert
  • Undelete

For Conga Orchestrate to use a custom object you've created, you must create a trigger and test class in a sandbox environment and deploy them to your production environment. Salesforce does not allow you to create an Apex trigger or Apex class directly in a production org. Refer to Deploy from Sandbox with Change Sets for instructions on the deployment process.

To create Custom Object as Step trigger in a sandbox environment

Follow these steps to create the trigger in a sandbox environment:

  1. In your sandbox environment, open Settings by clicking the gear icon (in Lightning) or your name (in Classic) in the upper right corner of Salesforce.
  2. Select Developer Console.
  3. Select File.
  4. Hover over New and choose Apex Trigger.
  5. Give your trigger a descriptive name, like CustomObjectNameAsStepTrigger.
  6. Choose the custom object from the sObject dropdown.
  7. Click Submit.
  8. Copy the following code and paste it into the new trigger window.
    trigger TRIGGERNAME on YOUR_CUSTOM_OBJECT_API_NAME (after insert, before insert, before update, after update, before delete, after delete, after undelete) { FSTR.COTriggerHandler.handleOrchestrateTrigger();}
  9. Replace TRIGGERNAME in line 1 with the name of your new trigger. This is the name you chose in step 5.
  10. Replace YOUR_CUSTOM_OBJECT_API_NAME with your custom object's API name.
  11. Save the trigger by pressing Ctrl+S on your keyboard or by selecting File > Save in the top menu of the Developer Console.
  12. Close the Developer Console.
  13. Ensure the correct configuration exists for your step or process object on the Conga Orchestrate Object custom setting. This setting dictates whether Conga Orchestrate uses the object as a process, as a step, or both.
Administrator Guide
Salesforce
Orchestrate

April 28, 2025