Thanks Robert for your response. I have communicated with my end users, and here is the feedback received
"When you use the shift+click, you are presented with two options — save/update and save/close. The expectation would be that save/update saves the record and updates it with the changes, but leaves you in the window, save/close would close the window.
An example of how this could be used is as follows:
User is working in a list that is sorted/filtered.
User takes a phone call about a job in this list.
Use the shift +click so you don't navigate away from the list and have to re-load this.
If they need to update the next steps in this job as it is resolved over the phone, they first have to apply a document type to generate the flow. As soon as they hit save/update to save the document type, the job closes down, so they have to locate it again, open it back up etc.
Another use similar to this is classifying the work. Some teams have an 'assigner' who determines who the job needs to go to, and could also potentially need to update the status of the job at the same time. Again, the job will close as soon as they save the document type, which they need to do to be able to progress the job."
This closing dialog upon save/update is still considered a defect, as it is expected to save or update the current record, not thing else. I would like to search for a possible out-of-box script (if feasible) to hopefully address this, or maybe have to wait for a new Fuji Patch if they are aware this has been considered an issue.
Kind regards,
