These Release Notes contain the following information about Conga Orchestrate Spring21.04.23 Release.
Packages: Lists packages that are required to upgrade to this release of the product
- System Requirements and Supported Platforms: Lists requirements and recommendations for installing this release
New Features: Provides high-level descriptions of new features introduced in this release, with links to more detailed information
- Enhancements: Provides high-level descriptions of enhancements to existing features
- Resolved Issues: Lists customer-reported issues that are resolved in this release or known issues resolved from previous releases
- Known Issues: Lists known issues that are applicable in this release
This documentation may contain descriptions of software features that are optional and for which you may not have purchased a license. As a result, your specific software solution and/or implementation may differ from those described in this document. Please contact your CSM or AE for information on your specific features and licensing.
The following packages and dependent packages are required to upgrade to this release to utilize all the new features of this release. These are the minimum required versions; later versions are also supported. Separate prerequisites for each feature can be found in the respective guides. The packages marked as (New) are new packages in this release.
Latest Certified Version
(Version Name | Version Number)
Conga Orchestrate (New)
System Requirements and Supported Platforms
The following table lists the minimum requirements for installing and using Conga Orchestrate.
Minimum Supported Version
Internet Browsers (latest stable version of):
There were no new features in this release. Keep checking the documentation portal for new updates.
There were no enhancements in this release.
The following table lists the issues resolved in this release.
|Conga Internal ID||Description|
|PROC-1755||If you cloned a record, Conga Orchestrate did not clone the related virtual steps.|
|PROC-1756||Queued Steps did not process all the steps if any one step failed. This issue is now resolved. If any step fails, the status of the step is updated to Error with a brief description, and the rest of the queued steps are processed.|
If you overrode the New buttons on Process Objects with Orchestrate's RTSelect pages, Account or Contact details were not passed on to the new Record when you created a new record from the Account or Contact record pages through a related list. This issue was observed in Salesforce Lightning Mode only.
This issue is now resolved. You can now create a custom button on the Contact or Account and pass the Account or Contact ID using defaultFieldValues parameter.
When you create custom buttons on RTSelect Pages, ensure that you use defaultFieldValues parameters to passs any field into the object. For example, to create a custom button on the contact page, use the following URL:
'Canceled' as object status was not supported. You can now spell the status as Canceled or Cancelled.
Conga Orchestrate displayed an error on executing delete query on standard step objects. This issue was observed because the query tried to access the name field on the object and certain standard objects do not have a standard name field.
Conga Orchestrate required Task object to contain Canceled or Cancelled value in its status field to navigate beyond the Getting Started page.
An object that was the Definition Process Object and a Step Object on that Definition inside a stage, and was without a process instance lookup, caused a null pointer exception when Conga Orchestrate tried to calculate Stage completion.
If the Status was propagated from definition onto Task Steps without Process Instance setup, Conga Orchestrate tried to access an incorrect object lookup field and did not update the Task Status.
Clause and Clause Bundle Steps stopped processing and gave exceptions in the following scenarios:
|PROC-1786||Conga Orchestrate created a duplicate stage child if your stage step contained two steps and the criteria for one of the field update step was satisfied.|
There were no known issues in this release.
DOC ID: ORCHSPR210423