Risk Identification workflow changes

Promita Das1
Tera Contributor

Hi,

I have requirement. Client don't want compliance mapping workflow to be shown as they're not using any policies and citations.
How to disable "Compliance Mapping" in Risk identification 

PromitaDas1_0-1779862235318.png

 

4 REPLIES 4

Tanushree Maiti
Giga Patron

Hi @Promita Das1 

 

Try this:

  1. Navigate to Workflow > Administration > Activity Actions.
  2. Search for actions with the Name Restart associated with the Risk Identification process.
  3. Locate the specific conditions that enforce these mappings and remove the  condition 

Can Restart = true

 

Refer: KB1705234 Not able to restart the risk mapping/compliance mapping in risk identification workflow - ... 

 

Check these links as well

IRM Risk Management > Implementing Risk Identification to capture risks related to business entities

https://www.servicenow.com/community/grc-forum/risk-and-compliance-relation/m-p/2708928

https://www.servicenow.com/community/grc-forum/risk-identification-being-created-in-the-information-...

 

Please mark this response as Helpful & Accept it as solution if it assisted you with your question.
Regards
Tanushree Maiti
ServiceNow Technical Architect
Linkedin:

jaikishan1
ServiceNow Employee

Hi @Promita Das1 :

You can try any of the following approaches as a customisation:

 

  1. Override RiskIdentificationUtils — Create a Script Include Override in the customer's scope that overrides _isComplianceInstalled() to always return false. This is a customization but is isolated.

  2. Deactivate the UI Action — Go to sys_ui_action → find "Associate Citations and Policies" (1bcbac590f821010580c95758b767edc) and set active = false. This hides the button that transitions to compliance_mapping state, but the state will remain reachable if users know how to set it manually.

  3. Inactivate the Process Flow Step — In the workspace Playbook process definition, deactivate the "Compliance Mapping" stage card (though this is harder to maintain across upgrades).

Regards,
Jai

 

Please mark this as helpful if it solves your query.

Regards,
Jai

1. Override RiskIdentificationUtils — Create a Script Include Override in the customer's scope that overrides isComplianceInstalled to always return false. This is a customization but is isolated.

Can you help me with the step

will it be a small change or a big enhancement?

Venky Kshatriy2
Tera Guru

Hi @Promita Das1 
Please go to the playbook designer, open the specific playbook, and delete the stage(Compliance) as needed. You can refer to the image below for guidance. However, since this is an out-of-the-box playbook, I recommend not deleting the compliance stage. Instead, consider copying the playbook and removing the compliance stage only from the version applied to your table, as this playbook may be used elsewhere.

VenkyKshatriy2_0-1779865860057.pngVenkyKshatriy2_1-1779865885971.png

If this response addressed your question, please mark it as Helpful and accept it as the solution.