How to change the application (scope) of a SLA Definition without needing to recreate the SLA DefinitionInstructionsTo change the scope (sys_scope) / application of a SLA Definition to bypass the need of recreating the SLA Definition entirely, follow the below steps: Isolate the record needing to have it's scope / application corrected.In the XML of the affected SLA Definition, the sys_scope data should look something like this (this is an example of values where the SLA Definition was in the HR Scope):<sys_scope display_value="Human Resources: Core">d4ac3fff5b311200a4656ede91f91af2</sys_scope>To change the scope to instead, say, global, run a script like the example script below in the Scripts - Background module:var gr = new GlideRecord("contract_sla");gr.addQuery("sys_id","3f0370019f22120047a2d126c42e706f"); // sys_id of SLA Definition heregr.query();while(gr.next()){gr.sys_scope = "global";gr.update();}After the script has been run, the XML of the affected SLA Definition should now look like:<sys_scope display_value="Global">global</sys_scope> By using the example script, the scoping issue was corrected without a need to recreate the SLA Definition.