"Vulnerability Severity" field not reflecting correct value as per Calculator rulesIssue Using Custom Vulnerability Calculators unable to update dot walked field on Vulnerability recordCauseWorking as designedResolutionTo summarize, we can only update VIT (Vulnerable Item) table fields from the customer defined Calculators. If you want to update TPE table as well, then the customer should rely on the script based definition for the same conditions. This is expected behavior. Below is the script how the rule gets evaluated behind the scenes. //Run this only on dev/qa, not on any other instances. (SAMPLE ONLY) - Please test and see if it suits your needs. gs.trace(true); var gr = new GlideRecord("sn_vul_vulnerable_item"); gr.get("09bbc491137c3300a23a7f176144b071"); //change sys-id //This is what essentially happens behind the scenes. for each setValue, it will be transformed like this. gr.setValue("risk_score",10); gr.setValue("non-existent", 1); //To show how non-existent fields are handled behind the scenes. gr.setValue("vulnerability.normalized_severity", 1); //Treated as non-existent on VI table. gr.update(); gs.trace(false);