In these release notes, you can find packages, requirements, features, enhancements, data model changes, fixed issues, and known issues for the Online Contract Collaboration (OCC) 2021.11.0 release. For documentation updates, see What's New in OCC Documentation.

This documentation may describe optional features for which you have not purchased a license; therefore, your solution or implementation may differ from what is described here. Contact your Customer Success Manager (CSM) or Account Executive (AE) to discuss your specific features and licensing.

To access the learning path, including overviews and demonstrations of this release’s updated features and enhancements, visit the Conga Learning Center.

Packages

The following packages and dependencies are required to upgrade to this release and use its new features. These are the minimum required versions; later versions are also supported. Prerequisites for each feature can be found in its documentation. Packages marked (New) are new for this release.

PackageLatest Certified Version (Name | Number)
Conga OCC

1.9

If you are an existing user, the OCC package is automatically upgraded.

Conga Contract Lifecycle Management (New)  

(Required if you use Conga CLM)

12.2.0654 | 12.654

Conga (CLM) Contracts for Salesforce (New)

(Required if you use Conga (CLM) Contracts for Salesforce)

2.61

Conga Approvals (New)

(Required if you use clause approvals feature)

12.2.0286 | 12.286


For more information on installing OCC managed packages, see Installing OCC. For more information on upgrading OCC managed packages, see Upgrading OCC.

OCC GA Release Configuration

By default, your production org references the GA version of OCC. If you have configured OCC for a preview release, you must change the OCC setting to use the GA version. 

To change your OCC Setting

  1. Go to Setup > Custom Code > Custom Settings > OCC Settings > Manage.
  2. Edit System Properties and update OCC URL as https://xajs.apttuscloud.com.

System Requirements and Supported Platforms 

For requirements and recommendations to consider before installing this Conga product suite, see System Requirements and Supported Platforms Matrix.

New Features

The following feature is new to OCC in this release.

Delete a Smart Clause

OCC now supports smart clause deletion. Smart clauses are part of a contract that can be reconciled between document versions and are noted in the agreement record. When you mark a clause for deletion, it is locked, and cannot be modified, swapped, or commented on until you accept or reject the deletion in true-up. Deleted clauses are updated to the agreement record and removed from the document.

For more information, see Deleting a Smart Clause.

Enhancements

The following enhancements are new to OCC in this release.

Identify Inserted or Deleted Clause Needing Approval

OCC can now identify the clauses that need approval if you insert or delete them from the document in OCC. The clause that needs approval should go through the approval cycle. You can see a blue Clause Approval Required tag on the top left corner of the clause and in the smart data pane, you can see a blue rubber stamp for that clause. If you click the blue tag on the clause or the blue rubber stamp in the smart data pane, you can see the associated approval process required. If you cancel or undo the insertion or deletion process, no approval required tag shows for the clause.

For more information, see Working with Clause Approvals.

Send an Inserted or Deleted Clause for Approval

You can send an inserted or deleted clause for approval when the Enable Clause Approvals comply system property is enabled and the Approvals managed package is installed. After you have installed the Approvals package in your org, you must configure Approvals to send clauses for approval.

You can send a clause for approval to multiple approvers. The clause approval can be sequential, parallel, or both. In the sequential process, OCC sends a clause approval request email to the first approver from the list of designated approvers. When the first approver approves the clause, OCC sends the approval request email to the next approver. In a parallel process, OCC sends a clause approval request email to one or several first-level approvers from the list of designated approvers. When all the first-level approvers approve the clause, OCC sends the approval request email to the next-level approvers. After the clause insertion or deletion request is submitted for approval, the clause remains locked for editing and true-up is disabled for that clause. The clause is again available for editing, swapping, or deleting after the approval cycle is complete.

For more information, see Configuring Clause ApprovalsWorking with Clause Approvals, and Comply System Properties.

Availability of Inserted or Deleted Clauses for True-up after Approvers Decision

OCC now enables you to accept or reject changes in true-up mode for inserted or deleted clauses after they are either approved or rejected by the approver. After true-up, the clause is available for editing, swapping, or deleting.

For more information, see Working with Clause Approvals.

Override the Existing Approval Process

OCC enables you to override the existing rule-based approval process and initiate an ad hoc approval process before submitting a request for approval. Switching to an ad hoc process lets you add approval steps, add users, roles, or queues to these steps, and route the approval sequentially or in parallel. You can save and edit ad hoc approval processes.

For more information, see Working with Ad Hoc Approval.

Precedence for Clause Approval Actions

You can perform multiple actions on clauses, such as inserting, updating, deleting, or swapping before submitting them for approval. These actions' orders of precedence are documented to help you perform several actions in the same session. 

For more information, see Precedence for Clause Approval Actions.


Data Model Changes 

There are no data model changes in this release.

Fixed Issues 

The following table lists the issue fixed in this release. If any actions are required, they will be listed in this table.

Case Number

Conga Internal ID

Description

00774329OCC-1666

When you open a document in OCC, the following error message displays:

An error was encountered while performing an operation in the UI. Please report this issue to support team, if it happens frequently.{"Message":"MERGE_SERVICE_TIMEOUT_ERROR : The remote server returned an error: (504) Gateway Time-out.","CorelationId":["4626d342-be3d-4ce4-8a81-164389e75cc0"]}. Error has been logged sucessfully.Error Reference Id : [ 6aff01cd-d595-4bc3-8357-3e68c05168ce ].

Known Issues 

The following table provides the cumulative list of known issues up to this release.

Conga Internal IDDescription
OCC-1706The context menu shows the "Delete Clause" option for an inserted clause before publishing the document.
OCC-1705The delete clause feature is not working for the documents that are imported offline. The document check-in fails and displays an error message.

OCC-1276

When a clause contains different bullet styles within a table, bullets are removed after the document is published.

OCC-1274

When a user inserts a clause with a table containing bulleted content, the bullet for an inserted clause disappears.

OCC-1254

When a user applies a left indent for a bullet point for a clause inserted in MS Word, the alignment goes out of the smart boundary in OCC.

OCC-1128

When a user deletes unnumbered bullets and publishes the document without redlines, the bullets are not deleted in the published document.

Workaround: After deleting the unnumbered bullets, accept the track changes.

OCC-953After opening a document in the Safari browser, the complete document was highlighted if a user highlighted any field using the smart data pane without clicking inside the document.
OCC-759In the Editing UI mode, when a user selects a picklist field value, the context menu is not available which allows adding comments for picklist fields in the document.
OCC-890

In Conga CLM (Contracts for Salesforce), a user cannot publish a document if there are duplicate clauses in the managed clauses.

DOC ID: OCC11.0RN20211110