Vimal Jain
ServiceNow Employee
ServiceNow Employee

 

 

Issue 

'Start Work' and 'Check In' Functions are throwing an error for Work Order Tasks - missing the script - global.FSMOnsiteUtil() 
 
Defect and CaseTask
DEF0436950  

CSTASK651448  
 

Release impact 

The issue is only reproducible in Utah instance on FSM Contractor mobile store app. 
 

Debugging/Investigation 

Check-in is the FSM feature available from Vancouver release. The changes are made in the Vancouver family release, but changes related to FSM contractor mobile store app are made as store release and with other features also shipped, the FSM contractor mobile 3.0.0 is certified for both U and V release, which is causing this issue.  
  

The issue is only reproducible in the Utah branch and is working fine in Vancouver and other future releases. 

 

Changes to Fix the issue 
This issue requires code fix in below meta data tables 
 
1.  Table: sys_sg_write_back_action_item 
         Name: “wot_start_work_param_screen“ 

 
2.Table: sys_sg_button_instance  

         Name: “My Tasks - Check-In FF” 

 

Customer can apply the update set provided along with this document.  
update set: “fixForContractorMobileUtahOnsiteIssue 
 
They can also verify and make the changes as shown below in the screenshot. 
After applying the changes in these places, we have observed that the issue is not reproducible. 

VimalJain_0-1694082277671.png

 

 

VimalJain_1-1694082277926.gif

 

 

 

IMPORTANT: An update set has been created on Utah OOB instance. If the instance is of a different build or any custom changes are present, please apply the changes manually referring to the screenshot below. 

 

Testing 
We have done complete sanity tests on OOB instance after applying these changes and we didn’t find any issues. 
Since customer instance could have custom code, it is expected that customer does entire sanity tests on their test/DEV instance, before moving the code to sub-prod/prod. 
 
Backport 

The issue is reproducible in the Utah instance. We are not doing any backport fix to Utah. 

 

Upgrade 
Customer would need to apply this update set/fix if they are upgrading to Utah release. Once they Upgrade to Vancouver, Customer should set Function instance:  My Tasks - Check-In FF , Active = true  
 
 
 

 

Version history
Last update:
‎09-07-2023 03:26 AM
Updated by:
Contributors