Conga Orchestrate Version 14 Overview
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.
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.CAUTION: 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 .
- 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.
- .
- Add Create From Lucidchart to the list of selected buttons.
- Add the Create from Lucidchart button to the Definition List view.
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.
After this screen, the rest of the setup process is the same as it was in Conga Orchestrate version 13.
