CHANGE tickets: "UPDATE" / "SAVE" / "SUBMIT" buttons lead to random cached page instead of reloading

[aldeluca]

When a user clicks on the "UPDATE" / "SAVE" or  "SUBMIT button, the ServiceNow page is not simply reloaded:
instead the user is redirected to a random page cached from previous sessions - is there any option to avoid this?

E.g. always reload the same ticket on "UPDATE" / "SAVE" or "SUBMIT" actions?

The use case scenario I have is that users would prefer the ticket to reload with the updates just entered, rather than lose sight of the current ticket. Any steer will be helpful.



CHANGE ticket buttons
#ADL2099

[Dr Atul G- LNG]

Hi @aldeluca 

Is any other tab open in same browser? This can be issue.

Submit and update will take you on last page where were you or pick up link from cache.

Save: will keep you on same page.

[aldeluca]

Thanks for your feedback, @Dr Atul G- LNG  - it doesn't solve my issue though
Adding more info below:

1. I've been able to systematically reproduce redirection of the user on a different page when clicking "Save" after a CHANGE ticket is created by copying from an older CHG ticket - this seems not expected based on your feedback too

2. If no tabs are open, it is not clear which page is cached:
    would there be an option to always redirect to a "home" page instead? 

3. Tabs can be open, yes - e.g. a user can have a "CHANGE>ALL" screen in a starting tab, listing the CHG tickets from a given filter and open two or three tickets of interest in tabs: this is normal browser functionality, is there any known restriction in that direction? I was expecting ServiceNow GUI to fully support multi-tab navigation if the browser does (issue verified with Google Chrome, Mozilla FireFox & Micorsoft Egde, all supporting tabs).