Auto-Reapprovals

Auto-reapproval enables you to return to a specific step in the approval process after restarting the approval, precluding approvers having to reapprove already-completed requests.

Auto-reapprovals occur at the step level when an approval process is resubmitted. This allows you to select where the approval process continues at a granular level. For standard step types, you configure the reapproval for the step; however, for subprocess or child process step types, reapproval is configured in the referenced approval rule.

Note:

For CPQ approvals, if the cart is approved, it must be in Ready for Finalization status for auto-reapprovals to work.

You can set auto-reapproval criteria such that a request approved by certain assignees is auto-approved based on the auto-reapproval criteria.

Auto-reapproval is extensible to cloned carts. The approval history of the original quote is also available at the cloned quote level: when you submit the cloned quote for approval, the system checks the approval history and the quote is auto-approved.

Note:

Cloned carts are limited to 600 approvals and 484 reapprovals.

Auto-Reapprovals Scenario

Example 1: Your approval process comprises three mutually dependent steps.

This step is configured such that all records with a 30–40% discount must be approved by John.
Once step 1 is approved, all records with a 41–50% discount must be sent to James.
Once step 2 is approved, all records above 50% must be sent to the CFO.

If you provide a 52% discount that John and James approved, but the CFO rejected, you do not want to reduce the amount and restart the approval process from step 1 (John). To avoid this, set up an auto-reapproval criterion such that:

Any discount where the current value equals a constant value of 50 is approved.
Any discount where the current value is less than or equal to the prior value is approved.

You can create an advanced condition such that if either A or B is satisfied, the request is auto-approved. Once you reduce the discount, steps 1 and 2 are auto-approved, and the request is forwarded for approval to the CFO.

Example 2: Enabling auto-reapprovals for proposal and proposal line items

You can submit approval requests for Quote/Proposal and Proposal Line Items for reapproval. If a quote or proposal is approved but the approvals manager changes the discount from 10 to 15% on a proposal line item, you can resubmit the approval request for this for reapproval.

The system honors the auto-reapproval criteria, using which a request once approved by certain assignees is auto-approved.

The updateApprovalData API reevaluates all the child record IDs (proposal line-item IDs in this case) for reapproval. For details, see Approvals for SOAP API Developers. This API is available in the base Approvals package and can be used with the optional Conga Proposal Auto-Reapprovals unmanaged custom package, available on request with Conga Release Management. This package contains the complete sample code that can be used along with the API in the base package to make auto-reapprovals work with proposals and proposal line items.

To configure reapprovals for approval rules

The approval rule must be of the Condition type. You cannot have reapprovals for Dimension types.

Go to an approval rule and click Manage Entries to raise the Rule Entries window.
Click New below Auto Reapproval Criteria to display the criteria options.

Select the fields and operators to create your expression:


Option	Description
Child Filter	This field's value is None unless child custom objects are associated with the approval rule's business object. If a child filter is available, selecting it populates the Field list with fields from the child object. Child filters do not support auto-reapproval. Whenever auto-reapproval is required, use a child process on line items or child objects.
Field	The fields available are related to the business object, or a child filter if one is selected. If you have defined Search Filter Approvals as entry criteria on your line item or child object, all corresponding child object fields are populated here.
Value Type (L)	Current Value uses the current value of the field to determine auto-reapproval. Prior Value uses the value of the field before the approval process was resubmitted to determine auto-reapproval.
Operator	Select operators carefully: for example, the Approval Stage field value cannot be greater than another field. If you select in or not in, the value list becomes a multi-select list and you can choose multiple values, if applicable. For example, if the field is Approval Status, you can select multiple values, such as Not Submitted and Pending Approval. To view the values, set a sequence number for the entry criteria.
Value Type (R)	Current Value and Prior Value are the same as Value Type (L). Constant Value means whatever you subsequently enter in the Value field is used for the expression, regardless of when in the approval process the field had that value.
Value	The value that is compared to Field/Value Type (L) to determine if the expression is true or false.

Click + to add another line to the expression and make it an AND relationship where each line must be true.

Click Advanced Options to combine OR and AND relationships between the lines of the expression.
Click OK to add the expression to the Auto Reapproval Criteria column.
Click Save to update the approval rule.

When your approval process contains an approval step that references the approval rule, auto-reapproval may occur based on the configured settings. You can add more auto-reapproval criteria for that approval rule entry or for any other entries for that rule.

To configure reapprovals for process steps

The approval process step type must be Standard.

Select an approval process and click New Approval Step.
Select Standard from the Step Type list and open the Select Auto-Reapproval Conditions page.

Select the fields and operators to create your expression:


Option	Description
Child Filter	This field's value is None unless child custom objects are associated with the approval rule's business object. If a child filter is available, selecting it populates the Field list with fields from the child object. Child filters do not support auto-reapproval. Whenever auto-reapproval is required, use a child process on line items or child objects.
Field	The fields available are related to the business object, or a child filter if one is selected. If you have defined Search Filter Approvals as entry criteria on your line item or child object, all corresponding child object fields are populated here.
Value Type (L)	Current Value uses the current value of the field to determine auto-reapproval. Prior Value uses the value of the field before the approval process was resubmitted to determine auto-reapproval.
Operator	Select operators carefully: for example, the Approval Stage field value cannot be greater than another field. If you select in or not in, the value list becomes a multi-select list and you can choose multiple values, if applicable. For example, if the field is Approval Status, you can select multiple values, such as Not Submitted and Pending Approval. To view the values, set a sequence number for the entry criteria.
Value Type (R)	Current Value and Prior Value are the same as Value Type (L). Constant Value means whatever you subsequently enter in the Value field is used for the expression, regardless of when in the approval process the field had that value.
Value	The value that is compared to Field/Value Type (L) to determine if the expression is true or false.

The Step Auto Reapproval Criteria field used to store reapproval criteria accommodates 32,000 characters.

Click + to add another line to the expression and make it an AND relationship where each line must be true.
Click Advanced Options to combine OR and AND relationships between the lines of the expression.
Click Next and finish configuring the approval step.

When you resubmit the approval process, the process automatically reapproves the appropriate steps when the auto-reapproval criteria are met.

Use Case: Auto-Reapproval for Agreement Approval Requests

Business Context

Short-term agreements need little oversight, but longer commitments carry more risk. Larger long-term agreements need an extra layer of review on top of the standard sign-off. Conga Approvals can trigger an approval process only for agreements with a longer term, add a second approver when the value is high enough, and reapprove one approver automatically on minor revisions while still requiring the other to take a fresh look.

Overview

This use case sets the approval process to trigger only when Term (Months) is greater than 12, configures a condition-based approval rule with two entries so every triggered agreement goes to the Sales Manager and high-value agreements also go to the VP of Sales, and adds auto-reapproval criteria to only the Sales Manager entry. Your implementation may vary.

Persona

Field	Details
Name	Aisha Bennett
Role	RevOps Administrator, Meridian Industries
Goal	Only trigger approval for agreements with a term longer than 12 months, add the VP of Sales as a second approver for high-value agreements, and let the Sales Manager's approval renew automatically on minor revisions while the VP of Sales always reviews manually.

Scenario

Meridian Industries only requires approval for agreements with a term greater than 12 months. Every triggered agreement needs Rachel Kim's (Sales Manager) sign-off. Agreements valued above USD 250,000 also need Marcus Chen's (VP of Sales) sign-off, in addition to Rachel's. Aisha configures auto-reapproval only on Rachel's entry, so a minor revision auto-approves her portion on resubmission. Marcus Chen's entry has no auto-reapproval criteria, so his portion always goes back to Pending on resubmission and he must approve it manually.

Prerequisites

The Conga Quote Approvals package is installed in your Salesforce org. For more information, see Installing Conga Approvals.
The Preview & Submit and My Approvals buttons are added to the Quote/Proposal page. For more information, see Configuring My Approvals and Approvals Pages.
The Agreement object is registered in all five Conga Approvals picklists in Salesforce Setup (Approval Process Object Label, Approval Process Object Type, Approval Rule Dimension Business Object, Approval Rule Business Object, and Search Filter Business Object). For more information, see Adding Values to Approval Pick Lists.

A record for Apttus__APTS_Agreement__c exists in Approval Custom Config (Setup > Custom Settings > Approval Custom Config).
A Currency field named Total Contract Value (cnga__Total_Contract_Value__c) exists on the Agreement object. If it does not exist, create it via Setup > Object Manager > Agreement > Fields & Relationships > New > Currency.
A Number field named Term (Months) (cnga__Term_Months__c) exists on the Agreement object. If it does not exist, create it via Setup > Object Manager > Agreement > Fields & Relationships > New > Number.

Create the approval rule. For more information, see Approval Rules.
1. Log in to your Salesforce org as an administrator.
2. Click the App Launcher and select Conga Approvals Setup.
3. Click the Approval Rules tab and click New.
4. Select Agreement as the Business Object and click Next.
5. Enter the rule details using the sample data below and click Save:
  
  Field Value
  Rule Name Contract Value Approval Rule
  Business Object Agreement
  Rule Type Condition
  Approval Policy Unanimous
  Rule Criteria Total Contract Value > 0
Note: Rule Criteria only references Total Contract Value. Term (Months) is not part of the rule; it is used separately in step 3 to decide whether the approval process triggers at all. Approval Policy is Unanimous, so if more than one entry matches an agreement, every matching approver must approve it.
Add rule entries to layer approvers by value. For more information, see Approval Rule Assignees.
1. From the Approval Rules tab, click Contract Value Approval Rule to open the rule detail page.
2. Go to the Related tab and click Manage Entries.
3. Add the two entries below and click Save:
  
  Label Condition (Total Contract Value) Type Value (Approver)
  Sales Manager Review Greater Than 0 User Rachel Kim (Sales Manager)
  VP Sales Review Greater Than 250,000 User Marcus Chen (VP of Sales)
Note: Sales Manager Review matches every triggered agreement, so Rachel Kim always reviews. VP Sales Review matches only when Total Contract Value is greater than 250,000. When both entries match, an agreement needs approval from both Rachel Kim and Marcus Chen before it is fully approved.
Create the approval process. For more information, see Creating an Approval Process.
1. From the main menu, select Conga Approvals Setup and click the Approval Processes tab.
2. In the Manage Approval Processes for dropdown, select Agreement, then click Create New Approval Process.
3. Select Rule Driven Process.
4. Enter the process name using the sample data below and click Next:
  
  Field Value
  Process Name Contract Value Approval Process
  Object Type Agreement
  Process Type Rule Driven
5. On the Entry Criteria page, add the condition below and click Next:
  
  Field Operator Value
  Term (Months) Greater Than 12
  
  Note: The Entry Criteria on the process is what triggers the approval. Only agreements with a term greater than 12 months enter the process; shorter-term agreements are submitted without an approval step.
6. Leave other options blank and click Next until your process is complete.

Field	Value
Rule Name	Contract Value Approval Rule
Business Object	Agreement
Rule Type	Condition
Approval Policy	Unanimous
Rule Criteria	Total Contract Value > 0

Label	Condition (Total Contract Value)	Type	Value (Approver)
Sales Manager Review	Greater Than 0	User	Rachel Kim (Sales Manager)
VP Sales Review	Greater Than 250,000	User	Marcus Chen (VP of Sales)

Field	Value
Process Name	Contract Value Approval Process
Object Type	Agreement
Process Type	Rule Driven

Field	Operator	Value
Term (Months)	Greater Than	12

Create the approval step and submission actions.

On the Approval Process detail page, click Add New in the Approval Steps section. For more information, see Creating Approval Steps.
Enter the step details using the sample data below and click Next through each wizard page, then click Save:

Field Value
Step Name Contract Value Review
Step Type Sub Process
Approver Rule Contract Value Approval Rule
Send Email Selected
Step Dependencies None (runs as the only step)

Field	Value
Step Name	Contract Value Review
Step Type	Sub Process
Approver Rule	Contract Value Approval Rule
Send Email	Selected
Step Dependencies	None (runs as the only step)

Add Initial Submission Actions, Final Approval Actions, and Final Rejection Actions using the sample data below:

Action Type	Field Action Type	Field Name	Value
Initial Submission	Field Update (Constant)	Approval Status	Pending Approval
Final Approval	Field Update (Constant)	Approval Status	Approved
Final Rejection	Field Update (Constant)	Approval Status	Rejected

For more information, see Creating Initial Submission Actions. Follow the same steps to configure the Final Approval and Final Rejection actions.

On the Approval Process Definition page, click Activate to make the process live.

Note: The approval process will not trigger at runtime until it is activated. Activation is a separate step from saving.

At this point, the base approval process is active. Agreements with a term of 12 months or less are submitted without triggering approval. Every triggered agreement requires Rachel Kim's approval. If the value also exceeds USD 250,000, Marcus Chen's approval is required as well. Step 5 below adds auto-reapproval for Rachel Kim's review only.

Configure auto-reapproval on the Sales Manager Review entry only.
1. Click the Approval Rules tab and open the Contract Value Approval Rule.
2. Click Manage Entries.
3. Locate the Sales Manager Review entry and click New below Reapproval Criteria.
4. Configure the condition using the sample data below and click OK, then Save:
  
  Entry Field Value Type (L) Operator Value Type (R) Value
  Sales Manager Review Total Contract Value Current Value Less Than or Equal To Constant Value 250,000
5. Do not add Reapproval Criteria to the VP Sales Review entry. Leave it blank so Marcus Chen's approval is never granted automatically.
Note: Only the Sales Manager Review entry has auto-reapproval criteria. Because the VP Sales Review entry has none, a resubmitted agreement always resets Marcus Chen's approval to Pending, regardless of value.

Entry	Field	Value Type (L)	Operator	Value Type (R)	Value
Sales Manager Review	Total Contract Value	Current Value	Less Than or Equal To	Constant Value	250,000

Agreements with a term of 12 months or less are submitted without triggering an approval process.
Every triggered agreement requires approval from Rachel Kim. Agreements valued above USD 250,000 also require approval from Marcus Chen.
If a previously approved agreement is revised and resubmitted at or below USD 250,000, Rachel Kim's approval is granted automatically.
Marcus Chen's approval is never granted automatically. Whenever his entry applies, a resubmitted agreement waits for his manual approval.

Entry Summary

Entry	Approver	Applies When	Auto-Reapproval
Sales Manager Review	Rachel Kim (Sales Manager)	Every triggered agreement	Reapproves automatically if resubmitted value is USD 250,000 or less
VP Sales Review	Marcus Chen (VP of Sales)	Total Contract Value > USD 250,000	Not configured — always requires manual approval

Resubmission Example: Dual-Approver Agreement

Submission	Total Contract Value	Sales Manager Review (Rachel Kim)	VP Sales Review (Marcus Chen)
First submission	USD 300,000	Approved	Approved
Second submission (payment terms updated, value unchanged)	USD 300,000	Reapproved automatically	Pending (requires manual approval)

Continue to Use Case: Auto-Escalation and Reminders for Agreement Approval Requests on top of this approval rule and process.

Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

Auto-Reapprovals

To configure reapprovals for approval rules

To configure reapprovals for process steps

Use Case: Auto-Reapproval for Agreement Approval Requests

Footer Section

Explore