{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":45964,"path":"security-management/vulnerability-response/exception-mgt-approval-rules.md","title":"Configure approval rules for Exception Management","bundle":null,"doc_type":null,"release":"australia","body":"\n# Configure approval rules for Exception Management\n\nStarting with Vulnerability Response v15.0, use the flow designer to approve exception requests for exception management, exception rules, and false positive management. If you are deploying Vulnerability Response \\(VR\\) for the first time, the flow designer is enabled by default.\n\n## Before you begin\n\nRole required: sn\\_vul.vulnerability\\_admin\n\n## About this task\n\nIf you are an existing VR user, the default option is workflow.\n\nIf you have deployed Vulnerability Response v15.0 or later, the value of the system property **sn\\_vul.flow\\_designer\\_activation** is set to true. This means that the flow designer is enabled by default.\n\nIf you are already using Vulnerability Response prior to v15.0, the value of this system property is set to false. You can activate the flow designer by changing the value to true.\n\n**Note:** You cannot revert to using the workflow after activating the flow designer. For a detailed comparison between the workflow and flow designer, see [Exception management workflow versus flow designer](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/ex-mgt-flow-designer-vs-workflow.md).\n\nTo use the flow designer, create rules using the Approval Rules module. Using this module, you can configure approval rules for each of the following exception management workflows.\n\n-   Exception request for remediation tasks\n-   Exception request for vulnerable items\n-   Exception rule\n-   False positive for remediation tasks\n-   False positive for vulnerable items\n\n**Note:** You can also define conditions containing multiple levels of approval within a rule. The flow designer automatically inherits the rules created in this module and processes the matching approval workflow. For information on configuring approval levels, see [Create approval levels for Exception Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/exception-mgt-config-approval-rule.md).\n\n## Procedure\n\n1.  Navigate to **All** &gt; **Vulnerability Response** &gt; **Administration** &gt; **Approval Rules**.\n\n2.  On the Approval Rules page, select the group for which you want to set the approval rule.\n\n3.  On the form, fill in the fields.\n\n<table id=\"table_imd_lrv_drb\"><thead><tr><th>\n\nField\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nName\n\n</td><td>\n\nApproval configuration name.\n\n</td></tr><tr><td>\n\nTable\n\n</td><td>\n\nTable on which the rule is applied.\n\n</td></tr><tr><td>\n\nApplication\n\n</td><td>\n\nDefault value is Vulnerability Response.\n\n</td></tr><tr><td>\n\nRule type\n\n</td><td>\n\nSpecifies the rule type. For example, exception management, false positive or exception rule.\n\n</td></tr><tr><td>\n\nActive\n\n</td><td>\n\nEnabled by default, signifying that the approval rule is in use.\n\n</td></tr><tr><td>\n\nDescription\n\n</td><td>\n\nShort description of the approval rules.\n\n</td></tr><tr><td>\n\nApproval expiry \\(days\\)Starting from v21.0 of Vulnerability Response\n\n</td><td>\n\nDate until when the approver can approve the request.\n\n</td></tr><tr><td>\n\nNotify approver \\(days\\)Starting from v21.0 of Vulnerability Response\n\n</td><td>\n\nDate after which the approver is notified to take action.\n\n</td></tr></tbody>\n</table>4.  Select **Update**.\n\n    In the Approval Configurations tab, there are two levels of approvers set up by default. You can select a rule to define the conditions based on different use cases within a rule. For more information, see [Create configurations for an approval rule](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/exception-mgt-approval-config.md).\n\n    **Note:** In each configuration page, you can create multiple approval levels. For more information, see [Create approval levels for Exception Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/exception-mgt-config-approval-rule.md).\n\n\n## Example\n\nBased on different use cases, you can define different approval processes for the same vulnerabilities found on different configuration items.\n\n"}}