Approval
When requesting an approval, Recruiting Center users must choose from a list the name of the individuals who will be required to do the approval. The list of approvers can be configured or not by the system administrator depending on the type of approval chosen by an organization.
If the standard approval process is used within an organization, the Recruiting Center user will select approvers from a list containing all of the active users of the database. The Recruiting Center user will also be able to create a list of frequent approvers in the My Setup feature.
If the Dynamic Approval Routing (DAR) process is used within an organization, the list of approvers is pre-populated upon selecting the Request Approval action. The list of approvers to be generated is configured by the system administrator within the Dynamic Approval Routing feature. These approvers are displayed based on configured rules and conditions.
The approval path can be carried out in two ways:
Sequential: When the first approver receives an approval request, he/she approves the item (requisition or offer). Once approved, the approval request goes to the next approver, and so on. The item does not move forward until each approver has approved it in the sequence defined.
Parallel: Multiple approvers receive an approval request and they can all approve the item at the same time. Approvers can approve the item without having to wait for the others.
If the standard approval process is used within an organization, the system administrator must activate settings to enable sequential or parallel approval. If Dynamic Approval Routing is used, the approval will be sequential unless there are more than one approver for the same role in which case the approval will be parallel.
All files requiring an approval are in PDF format. When conducting the approval from either the Tasks list or from eShare, the user will receive a PDF print version of the file to review (rather than the actual file being visible in the system). Also, approval files are generated according to the user's permissions to view fields having specific security levels.