Management Hierarchy Approval-Rule Attributes

When you define approval policies using the Manage Approval Transactions for Human Capital Management task, you can create one or more approval rules for manager hierarchies of predefined and locally defined types.

This topic describes the values that you can specify in the THEN statements of approval rules for manager hierarchies.

Attributes

The following table summarizes the attributes of the manager-hierarchy approval rules and their default values.

Attribute Name	Description	Values	Default Value
Action Type	Allows users to choose from Approval required (participants need to act on the transaction), Information only (participants get FYI notifications), and Automatic approval (participants do not need to act, transaction is auto approved).	Approval required Information only Automatic approval	Approval required
Route Using	Allows users to choose which manager to route through.	Resource manager Line manager Project manager Regional manager Customer—Defined Manager Types	Line Manager
Approval Chain of	Allows users to choose which approval chain to use.	Requester User Worker Worker's Current Line Manager Worker's Proposed Line Manager	Requester
Start With	Identifies both the first approver and the manager hierarchy. By default, approval requests are sent to the requester's first-level manager, and the manager hierarchy is the one associated with the requester's primary assignment. The requester is the worker who submits the transaction. If you select a user in Approval Chain of, then the manager hierarchy is the one associated with that user's primary assignment. For example, when promoting one of your direct reports you could select as initial approver a human resource (HR) specialist who is outside your manager hierarchy; approval requests from this rule would be directed to the manager hierarchy of the HR specialist's primary assignment. If you select a user who is not a manager, then the rule fails.	Manager Employee Second Level Manager	Manager
Number of Levels	Controls how far up the selected manager hierarchy approval requests are sent. The first level is based on the Start With value. Approval routing stops when either the number of levels or the topmost approver is reached, whichever occurs first.	Worker's Current Line Manager 1 or higher	1
Top Approver	Specifies an approver above whom approvals are not routed. Approval routing stops when either the number of levels or the topmost approver is reached, whichever occurs first. For the top approver value, you can select: A different manager (first-level or second-level, as appropriate). A user who is a manager from the same manager hierarchy as the initial approver. If you select a user who is not a manager or is from a different manager hierarchy from the initial approver, then the topmost approver is not found. In this case, routing of approvals stops when the number-of-levels value is reached.	Worker Worker's Proposed Line Manager Requester User Manager Second Level Manager	Manager
Set Outcome To	Specifies the outcome for automatic approvals. If you set this value to Approve, then all identified approvers are recorded as having approved the transaction, even though the approval is automatic. Similarly, if you set this value to Reject, then all identified approvers are recorded as having rejected the transaction.	Approve Reject	None