Approval Rule Assignees
The Manage Entries section of an Approval Rule designates assignees who will receive approval requests, based on the associated dimension and where they are called within an approval step.
You can have a user, role, queue, custom version of those, related user, or auto approval as an assignee. Like configuring assignees in the approval step, you can indicate whether they should only be notified or sent an email informing them they must decide on the approval.
If you want to automatically progress an item, you can select Auto Approval as an assignee and associate the rule with a sub-process in an approval step. In instances where approval routing is based on thresholds, an auto-approval assignee can ensure the process is handled correctly.
Be sure that valid values are entered or the expected assignees may not be notified as expected. While you can enter someone's name, username, or email address, use either the username (that they use to log into the system) or the email address associated with their account. These unique identifiers ensure correct user selection.
Configuring Assignees in an Approval Rule
Limitation: Referencing Related Object Levels in Custom User
When you configure a Custom User in an Approval Rule Entry, you can reference fields from only one parent object level (n+1) in the condition criteria. The system does not support referencing fields from a second-level or beyond related object (n+2 level).
Example:
- Supported:
Agreement_r.OwnerId_c(This field is available directly on the immediate parent object.) - Not Supported:
Agreement_r.Account_r.OwnerId_c(This field is located on a second-level related object.)
The rule entries are now in use by the approval rule.
Now that the approval rule has assignees, you can create an approval process and reference the approval rule and it will use values entered here to route the approval.
Setting Up Auto-Escalation for Rule Assignees
Set up auto-escalation on approval rules that will be used as sub-process (context header object) only. Do not set up auto-escalation on child process (child records or line items).
