How to move Calculator Rules of Risk Calculator?

MdA3
Tera Contributor

4 weeks ago - last edited 4 weeks ago

Hi All,

 

We have created a Risk Calculator for Application Vulnerability Response, where in we have 4 calculator rules which is calculating the risk score.

 

How to move this calculator rules to QA/Prod?

 

Once I'm taking export, we are only getting the XML of Risk Calculator not the Calculator Rules.

 

Thanking in Advance

Arbaz

0 Helpfuls
  • 362 Views
1 REPLY 1

Naveen20
ServiceNow Employee

4 weeks ago

This is a known behavior — when you export the Risk Calculator (from the sn_vul_calculator_group table), the child Calculator Rules that appear in the related list are stored in a separate table and are not automatically included in the export. You need to export them separately.

Here are the approaches to move both the Calculator and its Rules to QA/Prod:

Option 1: Export Calculator Rules separately via XML

  1. Open your Risk Calculator record.
  2. In the Calculator Rules related list, open each rule individually.
  3. Right-click the header bar on each Calculator Rule record and choose Export XML (or use the list view of the rules related list and export all from there).
  4. Import both XMLs (the Calculator + the Rules) on the target instance. Import the Calculator first so the parent reference exists when rules are imported.

Option 2: Capture both in an Update Set

  1. Make sure you have a current Update Set selected.
  2. Open each of your 4 Calculator Rules individually and make a small update (e.g., modify and save, or use "Save" to force a customer update entry).
  3. Verify in your Update Set that entries for both the Calculator Group record and all 4 Calculator Rule records are present.
  4. Preview and commit the Update Set on your target instance.

Option 3: Manual recreation (if the rules are simple)

If the rules use conditions-based (non-scripted) logic, it may be fastest to manually recreate the 4 rules on QA/Prod, especially if this is a one-time setup. Document the field, operator, value, and score for each rule before recreating.

Tip: You can verify the Calculator Rules table by navigating to <instance>.service-now.com/sn_vul_calculator_group_list.do and checking the related list structure. When using Update Sets, always confirm that the child records appear as separate entries in the update set before promoting — the platform doesn't always auto-capture related list children unless they are individually touched after the update set is active.

This is the same parent-child export gap you see with other ServiceNow constructs like Flow Designer actions/subflows, catalog items/variables, etc. — related list records live in their own table and need to be explicitly captured.

0 Helpfuls