These Release Notes contain the following information about Conga Orchestrate Winter20.01.21 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
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-1410||Conga Orchestrate gave an |
For approval loopbacks, you could incorrectly loop from the top step.
The Queued Steps batch job did not handle different types of process objects on the processed queued steps. This resulted in a query exception by querying the incorrect process object.
When Event Placeholder steps were executed, their child steps with no drill-up or drill-down criteria did not create a step if there was another step with drill-up criteria on the definition.
The caching methods used to drill-down criteria processing time did not use a unique key for each criteria. This caused false positives or false negatives on step criteria.
For example, a step may use the criteria of an executed step to say that the step was passed. This issue is now resolved.
There were no known issues in this release.
DOC ID: ORCHWIN200122