In these release notes, you can find new features and enhancements and fixed and known issues for the Conga Revenue Lifecycle Platform 202410.1.0 release. For documentation updates, see What's New in Conga Revenue Lifecycle Platform 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.
New Features and Enhancements
The following features are new to Conga Conga Revenue Lifecycle Platform in this release.
User Type
External user type is now renamed to Internal for improved usability. For more information, seeAdding and Activating Users.
Extensibility: Conga Hooks Rules
Introduced new service hook rules APIs that allow executing custom code based on data change events or scheduled triggers:
GET /api/extensibility/v1/servicehooks/rules/ {name}
If the recipient is a user group, you can now send notifications (email and in-app) to all members of the group. For this, you must enable the Is Send Email to User Group Members toggle for the relevant user group. For more information, seeCreating User Groups, Creating Email Notifications, and Creating In-App Notifications.
HTTP Helper: External Communication Enhancement
The HTTPHelper now allows certificate (X.509) to be included in request headers for external communications.
Workflow Activities: Send Email and Send Email by Template
The Send Email and Send Email by Template activities now support dynamic recipient email addresses. A new Expression option is available in the Recipient Type field, allowing you to use constants, variables, or formulas to dynamically set recipient email addresses. For more details, seeSend Email and Send Email by Template.
Enhanced Workflow Creation
Previously, you had to use type-ahead search to find an object when creating a workflow. Now, you can search for an object or directly select it from the available values in the dropdown menu. For more details, see Creating Workflow.
Enhanced Role-Based Access Control for Read Criteria
When querying data in a system with role-based access control (RBAC), the Read Criteria for all object permissions are now appended to the query. This ensures that only the data the user is authorized to access is returned. The inclusion of these permissions in the query acts as a security filter, ensuring compliance with access rules and protecting sensitive information.
For example, suppose an organization has a Contract object with fields such as Contract Name, Amount, Region, and Client Name. You can set the Read Criteria for the following user persona, who can view specific records based on their role:
Sales Team: Has access to all contracts across all regions.
Regional Managers: Can only view contracts related to their assigned region (e.g., North America). information.
