This problem only occurs on the second upgrade. On the first upgrade to Fuji Patch 5 or higher, the property is set correctly.
Steps to Reproduce
ServiceNow engineers were able to reproduce this issue using the following steps:
- Upgrade the instance to Fuji Patch 5.
During the upgrade, the glide.workflow.script.strict property is created and set to false.
- Upgrade the instance to Fuji Patch 6 or Fuji Patch 7.
During the upgrade, the glide.workflow.script.strict property is changed to true.
If the property is incorrectly configured after upgrading to Fuji Patch 6 or 7, setting it back to false manually resolves the issue.
To avoid the problem during a planned upgrade to Fuji Patch 6 or Patch 7, manually change the setting to create a customer update record that prevents the upgrade process from modifying the property. During a ServiceNow instance upgrade, properties that are changed by the customer are preserved. Manually changing the property triggers this protection, ensuring that the instance does not run into the problem described above.
- Navigate to the link below to access the setting directly.
- Change the value to True and save the record.
- Change the value to False and save the record.
For more information on upgrades, see Upgrades Best Practices.
Related Problem: PRB645417