Frequently Asked Questions

What do you recommend to get up and running with Orchestrate?

See Using Process Definition Quick Starts, which includes recorded videos for initial configuration and a process library you can use or clone.

Does Lucidchart work with Orchestrate?

Absolutely! See Lucidchart Integration with Conga Orchestrate to learn about creating new process definitions from Orchestrate.

Why does my email fail to send when using a Salesforce email template in a Send Email step?

In Send Email steps using Salesforce email templates, you must populate the process object's Contact field and add field mappings for the required object's contact lookup. This is required even if the email is only sent to a user. Failing to populate the Contact field yields the Email alert failed to send due to either no Contact or Lead specified or a Contact or Lead specified with a blank Email field error message.

Why is my new Definition not executing?

Ensure that the active checkbox field on the definition is checked. A definition does execute until the active checkbox field is checked.

Ensure that all definition conditions are met. A definition with defined definition criteria does not execute until all definition conditions are met.

I checked "Generate Email Notification" on my Create Record (Task) step. Why am I not receiving an email?

When using Orchestrate to create Salesforce Tasks, Orchestrate leverages Salesforce's native email reminder functionality. Salesforce designed the email notification to occur when one user assigns a task to another user. As a result of this functionality, task assignment email notifications fire when the user completing the parent task is different than the user assigned the child task. Task assignment email notifications are not sent if the assigned user is the same for each task.

 The email notification template is not customizable.

How does Orchestrate handle multiple users in the same team role (e.g., Salesforce Account Team)?

The best practice is to assign a single user per role for each account or opportunity team.

How is Conga Orchestrate's behavior different in Salesforce Lightning and Classic?

Although Conga Orchestrate works mostly the same in both Lightning and Classic, there are some differences.

For example, the ApprovalList component, which displays all approvals at the process object level, is only available in Lightning. For approvals on individual step records, such as tasks, the ApprovalItem and ChecklistItem communicate with the Lightning page view in real time. In Classic, the Task page requires a page refresh to see a change in status when the approval or checklist is completed.

How does the Conga Orchestrate work with other Conga products?

In most cases, if the Conga Composer, Conga Sign, Conga Contracts for Salesforce, and Conga Collaborate packages are installed and set up on Salesforce, these Conga products to work with Conga Orchestrate.

Minor setup items or limitations are noted in the application:

Can guest users use Conga Orchestrate?

No. Conga Orchestrate is not compatible with the Guest User profile in Salesforce Communities.

Licensing and Installation

How do I install the latest version of Conga Orchestrate?

Install Conga Orchestrate directly from the Salesforce AppExchange

How do I know I'm on the latest version of Conga Orchestrate?

Conga Orchestrate pushes upgrades to all customers when a new version of the application is available. The latest version is also available on the Salesforce AppExchange.

Do all users in my Salesforce Organization need a Conga Orchestrate license?

Not necessarily. Conga Orchestrate allows process steps to be assigned dynamically (such as by team roles and user lookup fields) and is not tied to specific users. It may not be possible to know in advance which user records a process touches and usage may change as the organization changes. Conga Orchestrate is installed with a site-wide license, giving all users in the Salesforce organization access to the application by default.

To identify Conga Orchestrate users, we look for application builders. Users are those who define processes and steps, are assigned to steps in a running process, or who access pages or objects included in the Conga Orchestrate managed package. This is identical to what would be required if Orchestrate explicitly assigned user licenses instead of using the site-wide license structure.



Stages in Conga Orchestrate enable you to group related steps to complete before a child step is kicked off. We've heard of Conga Orchestrate users grouping steps in stages for the way they appear in the Visual view. Using staging this way may have unintended consequences and is not recommended. Also, step-back loops cannot be used within a stage.

Custom Code

When using your own custom code with Conga Orchestrate fields, make sure all classes involved in querying for Orchestrate fields reference the same Orchestrate version. The managed package version is set to Apex Class (in the browser) on the Version Settings tab. These are pulled in automatically when your code references one or more managed packages. For more information, see Managing Version Settings for Apex.

Best Practices for Using Orchestrate with Flow and Process Builder

When using Flow and Process Builder, use Salesforce best practices for code, as these tools are a nice user interface to code that executes behind the scenes. For example, insert all records of the same object type in one insert, just as you would in code. Even if you are using sub-flows, try to do one insert. Additionally, avoid another update to the same object in the same transaction.

There are several more best practices to consider as you use these tools. Review the resources below as you design flows or build processes to work with Orchestrate-managed processes.

Known Issues

Flow or Process Builder and Orchestrate Update Limitations

Conga Orchestrate steps may not execute when an update comes from a flow or process builder. This happens when step creation conditions are used and the "Reevaluate When" option is set to Process Object Update. 

Definition Import

When importing a definition using Orchestrate's export tool, there is a known error with two identically named steps, one of which uses looping (either Go Back to Step or Go Back to Stage is specified). To avoid this error, give each step a unique name before exporting the definition, then reimport the definition.

Issue with Top-Level Record Update Steps

When generating Composer documents as a child step to a stage that contains clauses or clause bundles, record update steps may behave unpredictably. For example, a Composer document may not attach to a record. This is because three applications may be making updates to the same record at once. The workaround is to avoid using top-level record update steps when using these clauses in-stage with docgen setup.

Document Not Getting Attached with Record

Enabling the High Assurance flag in a profile and firing an Orchestrate Generate Document step triggers the step but does not attach the document to the record. To work around this limitation, disable the High Assurance flag.