Conga Orchestrate version 14 includes new features and enhancements to help improve your current processes. Take advantage of the new features described below.

Conga Orchestrate changes revolved around a new object, process instance.


  • If you have steps assigned to queues, also add the process instance to the same queues as the step's object type to create.
  • Upgrading from Conga Orchestrate version 13 to Conga Orchestrate version 14 requires you to first install Conga Orchestrate version 14.18.2. This installation is only required if you are currently on version 13 and are manually upgrading your org to version 14.
  • Salesforce has deprecated Workflow Rules in favor of its Flows product. Before any upgrade to version 14, you must deactivate legacy workflow rules and activate replacement flows as described in Disabling Workflow Rules.

If your custom code references Orchestrate fields, set the version of Orchestrate code referenced in the Apex class(es) to version 13, not version 14.

All fields formerly included in such objects as opportunity, contract, task, case, lead, and campaign are now removed to lighten the Conga Orchestrate installation and for you to set up only the objects you want to use.

New Features and Functionality

  • Some default fields shipped with previous Conga Orchestrate packages are now removed.
    • Fields are removed from the Case, Campaign, Contract, Lead, Opportunity, and Activity objects.


    • Upgrading from version 13 to version 14 deprecates fields previously shipped on the contract, lead, opportunity, campaign, case, and activity objects. This can result in issues if the deprecated fields are referenced in custom code or within field sets in an org.
  • Track automated process steps (such as emails, record updates, and document generation) without being required to use tasks.
    • Use the process instance related list for step track.
  • Tasks are now available in queues.
    • If it exists in your org, deactivate the existing "task_cant_be_queue" validation rule in the Setup > Object Manager > Step > Validation Rules > task_cant_be_queue step object.
  • Assign queues to approval and checklist steps
    • Easily assign approval and checklist steps to queues after adding the step, approval, or checklist object to the queue's available objects.
    • This queue shows up as Assignee Type on the step and your queue is on the list.
  • Create definitions from Lucidchart.
    • Add the Create from Lucidchart button to the Definition List view.
      • Object Manager > Definition > Search Layouts (for Salesforce Classic) > List View > Edit.
      • Add Create From Lucidchart to the list of selected buttons.

New Installation

On a new installation, the only objects available to use "out of the box" are the Business Process and Process Task objects. Both objects are shipped by default with Conga Orchestrate. Both objects have all the previously required fields, as well as a lookup field to the new Process Instance object.

To set up a custom object or standard object (such as opportunity, contract, or task) as a step or process object, navigate to the Conga Orchestrate Setup page and use the Configure Object link in the Advanced Setup section.

When adding a new object as a step, process object, or both, only a process instance lookup field and a status field are created in the object. If the object is a step object or both a step and process object, you must also create a lookup field to the process object(s) that the step is used for.

If you are using an existing field, you are given the option to map certain fields to fields that were formerly required and are subsequently filled out during execution.

These are the field mappings for selecting an existing object as a process object. If you map any of these fields, they are filled out during execution like objects previously were. The only fields actually created are the process instance lookup and status fields.

The status field is not created if you map an existing picklist field in its place on this screen.

After this screen, the rest of the setup process is the same as it was in Conga Orchestrate version 13.

Upgrading from Conga Orchestrate Version 13

When upgrading from Version 13 to Version 14, the aforementioned objects (contract, opportunity, lead, case, campaign, and task) retain the fields added to each with the Version 13 installation. You do not need to modify any existing process or step objects. After an upgrade, all processes run normally and all old fields remain populated as they were in version 13.

You can also manually add a lookup field to the process instance object, with the API name Process_Instance__c, to the process or step object if you do not want to go through setup.


You must add the process instance lookup field to an object before deleting the previously required fields from Conga Orchestrate version 13.

To upgrade an object and use it in version 14, run it through the setup process again. This adds a process Instance lookup field. You are now free to delete every field Orchestrate added to the object with version 13 (aside from many status fields), or you can keep all fields and the process instance lookup field. During execution, a process instance is made with all process data that Orchestrate needs, but those old fields also are populated as they were in version 13 if they exist or are properly mapped.

Assign administrators and users to the new Conga Orchestrate admin and user permission sets. After installation, this is done automatically for users who were assigned to the prior permission sets.

Upgrading from Conga Orchestrate Version 12

To upgrade from version 12:

  1. Upgrade to version 12.14.3:

  2. Upgrade to version 13.4.7:

  3. Upgrade to version 14.18.2:

  4. Upgrade to version 14.165:


  1. If you manually add the Process_Instance__c lookup field to an object that was configured with the old fields in Version 13, double-check that the trigger running it contains nothing but the following code snippet: FSTR.COTriggerHandler.handleProcessObjectTrigger();

    If the Conga Orchestrate trigger code was inserted into an existing trigger with other custom code created by a client, ensure that the Conga Orchestrate snippet changes to the code above (if not already thus changed).

  2. A process instance record is only created and attached to a process or step object if that object has a process instance lookup field with the API name Process_Instance__c. Conga Orchestrate does not allow that to be mapped to a field with another name. It must use that specific API name, but the field label does not matter.

  3. The process instance houses all information previously stored on the step or process object to give Conga Orchestrate the information it needs to execute definitions. This reduces the product's footprint on objects, reducing the previously required 14 (or more) fields to only 2 required fields and the process object lookup fields. To view data that was previously stored on the object, such as a definition that was executed, navigate to the process instance and check the definition field.

  4. The new process instance results in no changes to approval or checklist objects. These objects are outside the realm of step or process objects and therefore function the same.