New factor in Risk Assessment Methodology (RAM) - Approach
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi everyone, I am looking to add a new factor and replace an existing one within the Control Assessment section of my Risk Assessment Methodology (RAM). In our Dev environment: I cannot move the RAM back to the 'Draft' state because there are assessments currently in progress linked to it. From what I understand, ServiceNow prevents this to maintain data integrity for active assessments.
My questions:
What is the recommended way to handle active assessments when a RAM update is required? Should I create a completely new RAM or attempt to 'force' a state change?
What are the step-by-step instructions for migrating this change safely into Production?
I want to ensure historical data is preserved and that the transition to the new factor is seamless for users. Any insights or proven workflows would be greatly appreciated!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello @sibayanchak ,
In ServiceNow, once a Risk Assessment Methodology (RAM) is being used by active assessments, it cannot be moved back to Draft because the system protects historical data and scoring integrity. The recommended and safest approach is not to force any changes on the existing RAM, but instead to create or clone a new version of the RAM and make the required factor updates there. The old RAM should remain published so that current assessments can finish without impact, while all new assessments automatically use the updated RAM. This versioning approach ensures historical data remains intact, audit reports stay accurate, and users experience a smooth transition without disruption.
If this helps you then mark it as helpful and accept as solution.
Regards,
Aditya,
Technical Consultant
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Won't this impact the roll up score if we create a new version of RAM for any change requested?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @sibayanchak ,
As per the OOTB behaviour you are not able to move any assessment in Draft till the time we will not close all the Risk assessments attached with it. If you are not able to close it you may try the fix script below.
var gr = new GlideRecord('sn_risk_advanced_risk_assessment_instance');
gr.addEncodedQuery('risk_assessment_methodology='+ 'put_sys_is of your risk assessment Methodology');
gr.query();
while(gr.next()){
gr.state = 'retired';
gr.update();
}Once you close all the assessments then only you will get an option to move the assessment methodology to draft.
So if you find it helpful for you please mark it as helpful and accept the solution to close the thread.
Regards,
Sagnic
