Skip to main content
Conga Support

Conga Orchestrate Release Version 12 - July 13, 2018

ALL ITEMS LISTED ARE SUBJECT TO CHANGE ON OR AFTER THE RELEASE DATE

FEATURE DETAIL

Contract Object Supported as Process Object

Conga Orchestrate now supports the Contract standard object as a process object when creating PCE Definitions.  To build a Definition using the new Contract object, click the PCE - Definitions tab in Lightning or Classic, click the New button, and select Contract in the Object Name list in the New PCE - Definition screen.

Additional Dashboard Components

To review the additional reports, click (or display) the Dashboards tab, click the All Dashboards link, and then click the Conga Orchestrate Dashboard link.  In each Conga Orchestrate Dashboard component, click the View Report link to access the underlying report.

PCE Step Types Renamed

The Task or Custom Object step type has been renamed Create Record.  The Document Merge step type has been renamed Generate Document.  The Email Alert step type has been renamed Send Email.  PCE step types are accessed from the Step Type list in the Step Edit screen.

Conga Composer Document and Email Templates Available for Use

Conga Composer Template or Solution can be used in the Generate Document step, and a Composer Email Template can be used on the Send Email step in Conga Orchestrate.  To use a template, click the New PCE - Step button from a PCE - Definition record, select Generate Document or Send Email in the Step Type list in the General Information section of the screen, and then select Composer in the Template Source list in the Template section of either screen.

At this time, Conga Orchestrate does not support e-signature submissions as all transactions occur in background mode.

Custom Object Step Type Can Be Created Without Record Type

The Create Record step type in a PCE Definition can now use a custom object that does not have at least one record type. To allow Conga Orchestrate to use your custom object as a step object, use the following Configuration Assistant functionality:  From a PCE - Definitions view, click the New PCE - Step button, select Create Record in the Step Type list in the General Information section of the screen, and select [Your Custom Object] in the Object Type To Create list in the Step Information section of the screen. The Object Record Type To Create list defaults to Master if the object does not have a record type.

Approval Option Added to Create Record Step

Manage Completion With Approvals option has been added to the Step Edit screen for the Create Record step in a PCE Definition.  When this checkbox is selected, the Approval option is applied to the step and users can choose the Approval Status and Rejection Status from a list of the step object’s closed status values. They then use the Approvals component on the generated step record to approve or reject, along with notes for the decision. The Status of the step record will be set accordingly.

Setup Instructions

The Approval Status field displays a list of closed status values. Rejection Status displays a list of open status values. To set up, add the desired picklist values to the Status picklist for the Task or Custom Object used in steps.

For Tasks, select the Closed checkbox for any values that should indicate the Task is closed/completed.

For Custom Object steps, designate a custom value in the object’s picklist as closed by adding it to the Closed Status Values box on the Settings page.

On the Settings page, ensure the Include Non-Closed Statuses field is selected. This will allow you to create child steps from parent steps that are set to Rejected.

Repetition of Steps in a Process Eliminated using Looping

An update to Conga Orchestrate code allows a series of steps leading up to a branching step, such as an Approval step that can have two outcomes, to be automatically repeated without the user having to create a duplicate set of steps. For example, Step 1 fires Step 2 when Step 1 is completed.  Step 2 fires Step 3 when Step 2 is completed. When Step 3 is an Approval step that is rejected, the process loops, or returns, to Step 1.  Users are no longer required to recreate duplicate versions of Steps 1-3 as Steps 4-6 and add these steps as child steps when the Approval step is rejected.

Configuration Assistant Automates Custom Object Compatibility

The Configuration Assistant has been enhanced to speed up the time-to-value during the configuration of Conga Orchestrate.  Using Custom Objects as a process object and/or a step in a process is now automated. Formerly, users were required to add specific custom fields, as well as create and deploy trigger and test code. Now, users choose the object(s) from a picklist, allowing them to be up-and-running in minutes. To access the Custom Object setup interface, click the PCE - Settings tab, and then click the Custom Object menu item.

Setting Screens (Lightning) Consolidated into Single Screen

The Lightning Settings screen provides access to the legacy PCE-Settings items, new Advanced Settings, and the new Getting Started interface in from a central location. The screen includes access to the Configuration Assistant and is divided into several sections, including Setup InformationChatter OptionsPermissions and Sharing, and Process Summaries (Gantt View).   To access the Settings screen, click the PCE - Settings tab.

Translation of Screen Labels, VisualForce Text, and Error Messages

Conga Orchestrate offers front-end and back-end support for additional languages, allowing users to add language translations for labels in program screens and text in VisualForce screens, as well as information in error messages.

Terminology Standardized in Program Screens and Running Processes

The word Queued in all PCE Definition screens and all running processes was replaced with the word Delayed to standardize the terminology.  Previously, both words were used to describe the same functionality, with Delayed on configuration screens and Queued on running process records.

PERFORMANCE IMPROVEMENTS AND BUG FIXES

  • We’ve added numerous performance improvements and squashed a few bugs since the latest release. When we find bugs, we squash them and we’re always seeking new ways to make #Conga Orchestrate faster and more intuitive. 

We’ll push these enhancements to your org automatically.  We understand if you can’t wait - feel free to upgrade yourself by using the link at the top of this document.  Please take note of any manual customization steps. Sorry we cannot automate the entire deployment for you!

  • Was this article helpful?