Screen AutoRefresh after App Deployment¶

Summary¶

No longer get 500 errors on a screen if you are logged in when we deploy new features.

Problem¶

When we deployed new features into the App for a tenancy (which we do on a regular basis) and a user was logged into the app viewing a screen in their browser, when they returned to that open screen they would get a 500 error.

Solution¶

When we have deployed new features in the App, the next time a user goes back to the screen they will be automagically redirected to the Catalog screen, forcing a page refresh.

Leverage the Magic¶

No action by the user is required.

ADI¶

Whoot! No more support calls from the users about the 500 errors.

Customer¶

Yay! No more 500 errors that me wonder what I did wrong.

Video Demo¶

None