While using the ServiceMax Console App, if an SFM is operating in background instead of interactive mode, is causing a lot of side effects for user experience.
As seen below each time a background SFM transaction complets (with 1 user click) system leaves back orphaned tabs with a generic ServiceMax heading.
This has a risk in the sense the same record could exist as a tab with the correct heading as well as a generic heading, so not only user does not know what records refer to the 2 generic ServiceMax tabs (after 2 background SFMs have been used).
The expectation is that background SFMs should behave the same way as interactive SFMs, without having to increase steps in the workflow before users can get a less confusing overview of parallel work. And also without having to remember to close down orphaned tabs and manaully referh the old version of the tab,
What is the underlying problem do you intend to solve with this idea?
Improved workflow for parallel work for remote engineers using browser
How is the problem being addressed today, if at all?
users have to close down orphaned tabs and also refresh the orignal tab to make sure it shows the current version