Conga Revenue Lifecycle Platform 202409.1.0 Release Notes

Workflow: Automatic Field Value Suggestions

In the Field Set within a workflow activity, the system now suggests options for defining a field value based on the field's data type.

Activity Listing by Workflow Type

The Activities window now displays activities according to the selected workflow type. For instance, when you create a standalone workflow, only the activities compatible with the standalone type will be displayed. For more details, see Creating Workflows.

Workflow: Variable Management Layout Update

Updated the variable management layout to enhance usability for listing, creating, updating, cloning, and deleting actions. You can now add descriptions for each variable to provide additional context, and specify the number of decimal places for variables with a Decimal data type. For more information, see Defining Variables.

Defining a variable is now only possible after creating a workflow. Previously, users could create variables simultaneously with workflow creation.

Role-Based Access Control (RBAC) for Record Type

Role-Based Access Control (RBAC) for Record Type is a powerful feature that allows administrators to define and enforce access permissions at the record type level for different user roles.

Record type level access control enables administrators to limit users' access to specific record types when creating records. For instance, if an Agreement object contains two record types—Non-Disclosure Agreement (NDA) and Master Services Agreement (MSA)—an administrator can configure the system so that:

• All users can create records using the NDA record type.
• Only users with specific roles (e.g., Legal Team or Contract Managers) can create records using the MSA record type.

Record type level access control is managed through Permission Groups. By default, all record types within an object are accessible to all users who have access to the object. However, administrators can customize these permissions as needed.

You can also utilize the Record Type Permission APIs to set the record type level RBAC.

For more information, see Understanding Role-Based Access Control and Creating Permission Groups.

Improved Field-Level Permission Behavior for Grid and Detail Views

Updated the behavior of Field Permissions as follows:

• Edit Access: If you have Edit access, you can update field values directly from the grid or detail view by clicking the edit icon.
• Read Access: If you have Read-Only access, a lock icon appears in the grid view, and field values are disabled in the detail view. If you attempt to edit, the system displays a message when you hover over the field.
• No Access: If your role does not have Read and Edit permissions, the system hides field values in both the grid and detail views.

For custom object layouts created via CX Studio, field-level edit permissions set in CX Studio take priority over general permission group access. Even if your role's Permission Group provides Edit access at the field level, you will not be able to edit values in the grid view columns or the record detail view fields unless they are explicitly set as “Editable” in the CX Studio layout properties.

For more information, see Understanding Role-Based Access Control, Managing Data Grid View, and Managing Content Details View.