It would also be helpful if Abila tells us how to utilize this feature because it does not just automatically happen. Unless it's on the next update. More info than "Already exists" would be useful
It would be kinder if the response was recently added, not already exists, because it didn���t exist when this request was written.
910 N Harbor Dr, San Diego, CA 92101
(619) 544-9600 ��� www.midway.org
[http://www.midway.org/mail/facebook2.jpg] [http://www.midway.org/mail/spacer_10px.jpg] [http://www.midway.org/mail/instagram2.jpg] [http://www.midway.org/mail/spacer_10px.jpg] [http://www.midway.org/mail/twitter2.jpg] [http://www.midway.org/mail/spacer_10px.jpg] [http://www.midway.org/mail/youtube2.jpg]
In medical we utilize "Root Cause Analysis" in figuring out what the issue is, possible mitigation/solutions and ranking/risk analysis of those mitigation/solutions. For this issue a simple mitigation that directly resolves the issue is a "kick you off of the process/screen button". The button and dialog box(es) would be on the process screen that is "locked up", With the proper permissions, we have the ability to "log out" an individual user. Thus, extending this to a "user/process" should not be a stretch. Just add the QA to the routine so that posting started is completed prior to the kicking out. It is a focused solution that does not disrupt established processing routines. THUS, I suggest a new approach instead of expending resources in adding more layers (complications/exceptions) to what has been done.
I would like to clarification on which form you are referencing to close after the posting process has completed. Are you referring to the "Post Transactions" form where you select one or more sessions/batches to post?
You won't be notified about changes to this idea.