Frequently Asked Questions

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, the Contact field must be filled in on the process object in order for the email to properly send. This is required even if the email is only sent to a User. Failing to populate the Contact field yields this error message: Email alert failed to send due to either no Contact or Lead specified or a Contact or Lead specified with a blank Email field.

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 have "Generate Email Notification" checked 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 there is a different user completing the parent task than the user being assigned the child task. Task assignment email notifications do not fire 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 (i.e. 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?

The majority of Conga Orchestrate's functionality is the same in both Lightning and Classic, although there are some behavioral 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, they 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, having the Salesforce packages of Conga Composer, Conga Sign, Conga Contracts for Salesforce, and Conga Collaborate installed and set up is enough for these Conga products to work with Conga Orchestrate.

Minor setup items or limitations are noted within 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. The link to the Orchestrate AppExchange listing is here.

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 made available. The latest version is also available on the Salesforce AppExchange here.

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 not possible to know in advance which user records a process may touch and usage may change as the organization changes. Conga Orchestrate is installed with a Site-Wide License, providing all users in the Salesforce organization with access to the application by default.

To determine Conga Orchestrate "users", we look at users who are builders and users of the application. Users are those that define processes and steps, as well as those who are assigned to steps in a running process. In addition, those 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 vs. the Site-Wide License structure.

Tips

Stages - Stages in Conga Orchestrate allow you to group related steps to complete before a child step or steps is kicked off. We've heard situations where Conga Orchestrate users are grouping steps in stages purely for the way they appear in the Visual view. Using staging in this way may have unintended consequences, and is not recommended.

Custom Code - When using your own custom code with Conga Orchestrate fields, make sure all of the classes involved in querying for Orchestrate fields reference the same Orchestrate version. The managed package version is set on 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 these tools, 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 as you utilize these powerful tools. Review the resources below as you design Flows and/or Process Builders that are designed to work alongside or interact with Orchestrate-managed processes.

Known Issues

  • Process Builder and Orchestrate update limitations
  • Conga Orchestrate Steps may not fire when the update comes from Process Builder. This applies in cases where Step Creation Conditions are used and the Re-evaluate When option is set to Process Object Update. In these scenarios, Steps may not fire.
  • Definition Import
  • When importing a Definition using Orchestrate's export tool, there is a known error where there are two identically-named Steps, and one of those Steps uses looping (i.e. has a Go Back to Step or Go Back to Stage specified). To avoid the error, give each Step a unique name prior to exporting the Definition, then attempt the import again.