Set up dynamic approval configuration on a policy record
Summarize
Summary of Set up dynamic approval configuration on a policy record
Starting with the Zurich release, ServiceNow enables dynamic approval configuration on policy records within the Policy and Compliance Management application. This feature allows organizations to define multiple approval levels and rules that adapt dynamically based on policy attributes such as type, state, and owner. Dynamic approval configuration replaces the traditional manual, single-level approval process by automatically assigning approvers and managing multi-level approval workflows, which enhances efficiency and accuracy in policy approvals.
Show less
Key Features
- Multi-level Approval Configuration: Define multiple sequential approval levels, each with specific approvers and rules tailored to the policy’s context.
- Dynamic Approver Assignment: Automatically assign approvers based on dynamic conditions related to policy fields, avoiding manual entry and reducing errors.
- Integration with Approval Configurator: Use the Policy Approval Rules module to create complex approval rules, including selecting individual users or groups from policy-related fields.
- Flexible Approval Methods: Choose between using specified approvers on the policy record or leveraging approval rules for dynamic determination.
- Approval Workflow Management: Policies transition to an "Awaiting approval" state, and approvals progress through configured levels until final publication or rejection.
- Redlining Support: Dynamic approval configuration is compatible with policies that have redlining enabled, ensuring comprehensive document control.
Practical Benefits for ServiceNow Customers
- Adaptability: Approval processes can adapt to changing organizational structures and policy conditions, ensuring relevant stakeholders are involved.
- Reduced Administrative Overhead: Automating approver assignment and multi-level workflows minimizes manual effort and accelerates decision-making.
- Improved Governance: Multi-level approvals provide thorough review cycles, which is critical for complex or high-risk policies.
- Error Reduction: Dynamic configuration avoids the pitfalls of single-level manual approvals, decreasing the chance of oversight.
- Access Control: Only users with appropriate roles (e.g., sncompliance.manager, sngrcappr.admin) can create or modify approval rules, maintaining security compliance.
Implementation Guidance
- To enable dynamic approvals, set the policy’s approval method to "Use approval rule".
- Create an approval configuration record and define approval levels and rules using the Policy Approval Rules module.
- Assign approvers dynamically or manually at each approval level based on your organizational needs.
- Monitor approval statuses via the Policy approval table, which tracks each level’s state and manages policy transitions.
- Ensure users involved in approvals have the necessary roles for access and action.
- If no valid approval configuration is found for a policy, an error is displayed and manual intervention is required to assign approvers or create configurations.
Typical Use Cases
Dynamic approval configuration is especially useful when policies require reviews from multiple distinct teams or departments. For example, an HR-related policy might require sequential approvals from HR, Compliance, and Legal teams. This setup automates the handoff between approval levels, reducing delays and improving governance.
A policy is a set of guidelines and rules established by a business organization to govern its operations. Creating an approval configuration record for a policy enables you to define one or more approval levels and approval rules based on various dynamic conditions.
Beginning with the Zurich release, you can set up dynamic approval configuration on a policy record. The policy table consists of the policy records that regulate the status of the policies. Before implementing a policy, it goes through a review and approval process.
Setting up dynamic approval configuration on a policy record enables you to define multiple levels of approvals based on various dynamic conditions such as policy type, state, and owner that are related to the policy fields. When you set up dynamic approval configuration on a policy record, the approvers for a policy are added dynamically to the policy record.
Limitations of adding the approvers manually
- The approval configuration process uses a single level of approval. If multiple levels of approval are not used, it increases the possibility of introducing errors and oversights in the approval process.
- The approvers for a policy cannot be changed based on dynamic or changing conditions of the approval process.
- The approvers are added manually to the record. The process can be time consuming, especially in large organizations or complex decision-making structures.
- Adding the approvers manually can lead to significant delays. Waiting to receive all approvals can slow down the decision-making process and decrease productivity.
Benefits of dynamic approval configuration
- Organizations often encounter dynamic and changing environments. Having the flexibility to change the approvers allows the approval process to adapt to shifting circumstances. It ensures that the most appropriate individuals are involved in the approval process at any given time.
- For complex or high-stake decisions, configuring multiple levels of approvals enables the reviewers to conduct a comprehensive review of relevant factors. It ensures that the decisions are not rushed and that the potential impacts are carefully assessed for different scenarios.
- Changing the approvers dynamically can streamline the approval process and reduce the administrative overhead, thereby saving time and resources.
Use cases for requesting multiple levels of approvals
Approval configuration can help create complex approval levels without manually adding approvers for each policy. In some cases, a policy owner may want to conduct multiple levels of approvals for a policy. For example, a policy is related to the HR domain. The compliance team, legal team, and HR team want to review and approve it. The policy owner can assign the HR team as Level 1 approvers of the policy.
When the HR team approves the policy, it is assigned to the Compliance team for Level 2 approval. It is then assigned to the legal team for Level 3 approval of the policy. Also, the policy owner may want to select the approvers dynamically based on certain rules that match with the policy.
This use case highlights the importance of integrating dynamic approval configuration with a policy and configuring the policy approval rules with Approval Configurator.
Approval configurator
To use the approval configuration, the approval method on the policy should be selected as Use approval rule.
Approval configuration should be created for the policy and valid approval rules should be configured for the users.
Use the Policy Approval Rules module to configure the approval rules.
Configuring policy approval rules using Approval Configurator
- Set up multi-level approval rules based on dynamic conditions.
- Send approvals to a user or a group of users selected from a field from the source record or select the user or groups manually.
- Set up only one approval or all approvals as required approvals.
- To set up an approval configuration record, see Set up an approval configuration record.
- To assign an approval level for the approval configuration record, see Assign an approval level for the approval configuration record.
- To set up an approval rule for the approval level in the approval configuration record, see Set up an approval rule for the approval level.
For more information on the roles in the GRC: Approver Configurator application, see Roles installed with GRC: Approver Configurator.
Roles required for creating policy approval rules
- A user with the sn_compliance.manager role can create policy approval rules with the sn_grc_appr.admin role.
- Users with the sn_grc.business_user and sn_grc.business_user_lite and above roles can view a policy.
- A user should have mp_document_user with either the sn_grc.business_user or sn_grc.business_user_lite role to access the document when redlining is enabled.
Workflow for setting up approval configuration
When you set up approval configuration on a policy record, the workflow contains the following steps.
- When an approval is requested for a policy record, the state of the policy changes to the Awaiting approval state.
- If the approval method is selected as Use approvers, it uses the approvers mentioned in the policy record.
- If the approval method is selected as Use approval rule, it checks for a valid configuration that suits the policy record. The dynamic approval configuration searches for the approval configuration record that is related to the policy.
- The dynamic approval configuration then retrieves the approvers from each approval level record and sends an approval request for each level.
- If a valid configuration is not found, an error message is displayed that there is no valid configuration for the policy.
If you are the policy owner, you can select the approvers for the policy in the Approvers field of the Policy form. The approvers are usually the users who have the Compliance User role. If you do not have proper access, you cannot access the policy record. To request access to the policy record, you must contact the Compliance Administrator.
Integrating dynamic approval configuration with a policy
To integrate dynamic approval configuration with a policy record, you can set up multiple approval levels and for each level, you can set up the approval rules. Based on the approval levels and rules setup, the approvals are triggered automatically. When one level is approved, the policy record is submitted for the next level of approval.
- When an approval is requested for the policy, the state of the policy changes to the Awaiting approval state.
- The dynamic approval configuration searches for the approval configuration record that is suitable to the current policy.
- If dynamic approval configuration is not set up on a policy record or even though it is set up, it is not applicable to that particular policy record, an error message is displayed that no valid configuration is found for the policy record and the record gets aborted. Users have to go back to your policy record and select the approvers or create a valid configuration for the policy record.
- If dynamic approval configuration is set up, the approvers, approval levels, and rules are added based on the configuration of the approval configuration record.
Components used for dynamic approval configuration
- The Policy approval rules module creates or checks the approval configurations with the source table as policy.
- The Policy approval table stores the approvers of each level of the approval configuration. It can be used for tracking the status of the approval levels.
- Based on the current level decision, the policy either gets forwarded to the next level of approval or if it gets rejected, it is reset to the Draft state. If all levels are approved, the policy moves to the Published state.