New Features and Enhancements
Approvals for Conga Platform offers these new features and enhancements in the 202406.2.0 release.
Recall Updates Quote-Level Approval Status to “Approval Required”
When the user recalls a cart approval, the approval is canceled and the quote’s approval status and approval stage field become Cancelled and Approval Required, respectively, maintaining functional parity with Salesforce. See To recall an approval.
Rejected Cart Resubmission
When a cart is rejected on a quote/proposal with its approval stage and approval status rejected, resubmitting “Approval Required” in the rejected actions for cart approvals changes the final rejection action status from “Approval Required” to “Rejected”.
My Approvals Context Record Link Inserted into Assignment Emails
A link is inserted into approval assignment emails directing the user to the My Approvals page requesting approval, giving the approver direct access to the approval request’s My Approvals page. Hyperlinks to the My Approvals page appear in the standard assignment, reassignment, reminder, and escalation email templates.
Rule Assignee-Level Support for Escalations and Reminders
You can now develop more granular escalation and reminder flows that reach individual rule assignees (approvers), rather than entire rule-entry-level recipient classes. See To create or edit rule entries.
Custom User Assignee Objects
We introduce an administrative setting to accept a list of platform objects that define a Custom User assignee. This setting is accessible by an API call to {host}/api/approvals/v1/system-properties/product-settings/{businessObject}.
In the Approval Rule context, the administrator can select a related-user assignee for the system to pick up at runtime and can enter a string that serves as a dot-notation leading to the user field from the context object. Both out-of-the-box and custom fields are supported and up to five levels of object relationship may be traversed. See To add a related user to a rule entry.
In the Approval Flow context, the administrator can select a related-user assignee for the system to pick up at runtime and can enter a string that serves as a dot-notation leading to the user field from the context object. Both out-of-the-box and custom fields are supported and up to five levels of object relationship may be traversed. See To add a related user to a flow entry.