After new Deployments - please check for Customizer Conflicts

  • 25 March 2022
  • 1 reply
  • 67 views

Userlevel 7
Badge +21

After deploying a new release such as a hotfix release, sometimes overlooked is whether there are Customizer changes that are now in conflict with the new release.  This can be identified by logging into the Alliance Browser as a customizer, going to the Customer menu and using the Conflict Resolver.

If there are conflicts, they will be listed and you can select which conflicts to resolve.  When this is completed, the resolved conflicts are placed into the DEV branch (not Public) for you to review and accept.

When the changes are accepted in the Dev branch, publish the Customizer changes again to make them available for other users.

This should be done every time after a deployment of new releases to avoid issues caused by missing Customizer customizations.

 


1 reply

Userlevel 7
Badge +15

And to follow up on that...if the shipment you are deploying contains a Mobile Edge installation executable and you are currently using the Mobile Customizer application then be sure to log in and test your existing mobile customizations on the STAGING URL to ensure that they are still working as you expect.  Once they are validated then click on the Publish icon to roll those changes out to the mobile technician’s devices in the field.

Reply