Skip to main content

Hi Team,

After Deploying Client Script it is required to do initialization in Mobile?  How can we achieve the changes without doing initialization. 

The Customer query is , it is very difficult for them to communicate  to the end users to do the initialization  after each deployment of Client Script/ Mobile Design in FSM.

Hi @TatKhandM 

After changes to the design need to initialise the mobile clients.

As an FSM admin you can do this from the smart client → Mobile Dashboard

 

 

Cheers!


After deploying a new client script or making changes to existing client scripts, in order to get the latest changes on mobile, users need to perform ‘Refresh Script’ from Designer, more precisely on the screen where the script is deployed. The ‘Refresh Script’ acts a Refresh Cache for the mobile app. However, the ‘Refresh Script’ option/ Designer option is only available to users who have ‘STUDIO’ license assigned to them. For users who do not have STUDIO license, a manual initialization has to be performed.

To avoid having multiple users perform initialization, we can use the ‘Mobile Dashboard’ screen on the Smart Client/ Web Client to choose the users and devices that need to be initialized. From there, we can trigger initialization to those devices where the updated script is to be deployed. 


Hi @TatKhandM ,

A couple of additional thoughts to keep in mind.

First, changing a client script is, in effect, creating a new solution for your users.  This is not something you should be doing without a change control process, just as if you were upgrading software versions.  Short of a production emergency fix, I’d recommend a scheduled process so that all users know they are getting a change and will need to Initialize when the change is available.

Second, the other contributors are correct that you can Initialize users from the Mobile Dashboard.  However, I think it worth mentioning that you need to be VERY careful doing this.  An initialization wipes all data from the device.  If users having pending, un-synced updates, they will be lost if you force an initialization from the back end.


Reply