VR - bulk edit "There are no approvers configured to approve this request. Contact your system administrator." error is shown when target State = "Deferred"Issue 1. Go to sn_vul_vulnerable_item table list view 2. Manually select n number of VITS (please select more than one) 3. Click "Bulk edit". 4. On the Bulk edit dialog, fill out the following fieldsa. Record selection - Only selected Vulnerable Itemsb. State - Deferredc. Reason - Risk Acceptedd. Short description - Anythinge. Until - Any future datef. Justification notes - Anythingg. Work notes - Anything 5. Click "Ok" Desired BehaviorAble to perform Bulk edit for selected VIs. Unexpected/Actual BehaviorAn Error is is displayed on top of the dialog - "There are no approvers configured to approve this request. Contact your system administrator.ReleaseXanaduCauseOut-of-the-box (OOB) behaviour triggered by a validation when target State = "Deferred"ResolutionSetting VIT state =12 = Deferred is requesting exception. And this requires an approval process for which an exception approver is needed. See relevant documentation below: Defer a vulnerable itemhttps://www.servicenow.com/docs/csh?topicname=defer-vul-item.html&version=latest Add an exception approverhttps://www.servicenow.com/docs/csh?topicname=add-exception-approver.html&version=latest The validation is in UI Page: BulkVulnUpdateDialog. UI Page: BulkVulnUpdateDialog/sys_ui_page.do?sys_id=66fe016f6701030017f141119585efe7 When state = 12 = Deferred is selected from the the Bulk Edit dialog. The UI page client scripts checks for below. ===if (!exceptionApproverL1GrpHasUsers) {showErrorMessage(getMessage("There are no approvers configured to approve this request. Contact your system administrator."));return false;}=== Above calls Script include: ExceptionSettingsAJAX.retrieveExceptionSetting()/sys_script_include.do?sys_id=e920c92153250010f255ddeeff7b1259 Which returns null/false for "hasUserForExceptionApprovalL1" in the instance because below does not return anything. Group members: /sys_user_grmember_list.do?sysparm_query=group%3Db275c59553a10010d1eaddeeff7b1283&sysparm_view= To test, you can add member to the group below and now should be able to continue without the message popping up. Group: Exception Approver - Level 1/sys_user_group.do?sys_id=b275c59553a10010d1eaddeeff7b1283