Plugin: "Best Practice - Change Risk Calculator" is not available and is there a way to automate Risk recalculation on field change?Issue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Currently, risk is set to moderate on changes, and only changes if the user manually runs another risk evaluation. We were exploring ways to make this onChange of the CI or business service, and Plugin below is referenced in the doc site, but can’t seem to find it in the plugin app manager, the classic app manager, or the store. Plugin: Best Practice- Change Risk Calculator pluginRisk Calculator property (https://www.servicenow.com/docs/bundle/xanadu-it-service-management/page/script/server-scripting/reference/r_ChangeRiskCalculator.html) Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } All Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } We got the following answers back from our Product team. 1. Outdated and inaccurate documentation. === Yes documentation is incorrect: https://www.servicenow.com/docs/csh?topicname=activate-change-risk-calculator.html&version=latest "Best Practice - Change Risk Calculator" plugin was renamed: "Change Management - Risk Calculator" === *** Request to update the documentation has been submitted. 2. Business Rule: "Run Risk Calculation" is no where to be found. So when glide.ui.risk_calculate_rule = business_rule, what BR is executing? === The Change Risk Business Rule was created for the Legacy deprecated Risk Assessment feature which could not evaluate risk on submit (code written 14 years ago and has been replaced with new Risk Assessment 8 years ago). Again we will update the docs, but please try not to use this approach. === 3. In the System Property: glide.ui.risk_calculate_rule, mentions "While this property allows for using a business rule to trigger the calculate risk action on insert/update, we do not recommend this method, because it requires precision alignment across the various risk methods. For example, a matching Risk Assessment requires human interaction which means that risk can no longer be evaluated automatically" => can you please expand on this with an example. This is not clear why this is being discouraged. === Discouraged because: Risk Conditions are a fully automated process insofar as no human interaction is required for them to run. Risk Assessments are a fully manual process where a human interaction is required, i.e. completing the Assessment. When both Risk Conditions and Risk Assessment match a Change Request, even when the properties have enabled Business Rule rather than UI Action driven risk evaluation, the UI Action overrides the Business Rule (because a human interaction is required). === 4. Do we have have any OOB feature to support Auto risk calculation when a field is updated on the form? I have already suggested a client script and use existing logic in the existing UI Action. === No there is not yet a good support for automatic risk calculation. The main reason for this is the purpose and consumers of the risk value? Generally there are three consumers, those who are approving a Change Request (whoever clicks the approve/reject button), from this point a Change Request should have all fields that affect risk, read-only e.g. CI/Service, affected CIs/Services, planned start/end dates, assignment groups and users etc, because if something has evaluated to low risk, and an approver approves that change request, using risk field as at least part of a reason for their decision, if this risk value changes later, and the change fails, the approval was given based on altered data. The second consumer is the person that implements the risk, giving that person more information on how "careful" they need to be. Finally there is often a dashboard/report that matches Change Request outcome to risk to see how effective risk evaluation was. Again if risk changes automatically on every field update and changes it value, these three consumers are not synced. ===