The employee switches the process status when the process is already switched and does not see the error
Good afternoon
There is such a problem, two employees opened the process at the same time and change its status, take the order to work. The first employee performs an action - the status changes, while the second employee, when clicking on the same "In Progress" button, does not receive an error that the Order is already in a different status, but sees that the changes have been saved, respectively, does not even assume that he did not change the status (and can no longer work with the order). Although it should receive an error, since at the current stage of the process there is no longer a Take on button. I am attaching the video. Please fix this
Original question is available on version: ru
There is such a problem, two employees opened the process at the same time and change its status, take the order to work. The first employee performs an action - the status changes, while the second employee, when clicking on the same "In Progress" button, does not receive an error that the Order is already in a different status, but sees that the changes have been saved, respectively, does not even assume that he did not change the status (and can no longer work with the order). Although it should receive an error, since at the current stage of the process there is no longer a Take on button. I am attaching the video. Please fix this
Answers:
Shatokhina Irina wrote:
Although it should receive an error, since at the current stage of the process there is no longer a Take on button.
Should receive an error if it tries to switch to a status that is not equal to the current one and there is no transition to it from the current status (for example, when they want to switch to different statuses)
If you do some checks on your situation, it's hard for me to imagine how many bad "side" effects from this will be, even in the same crowns. And in theory, everything is logical - he is trying to switch - the status is already equal to the desired one - OK.
The only thing I can suggest to you is probably to look for an action that checks the value of the field BEFORE switching the process status (to fill it after switching and give an error when it is fired again and the value is present).
08.04.2021, 11:04
Original comment available on version: ru
Tyndyk Maxim Vadimovich wrote:
Shatokhina Irina wrote:
Although it should receive an error, since at the current stage of the process there is no longer a Take on button.
Should receive an error if it tries to switch to a status that is not equal to the current one and there is no transition to it from the current status (for example, when they want to switch to different statuses)
If you do some checks on your situation, it's hard for me to imagine how many bad "side" effects from this will be, even in the same crowns. And in theory, everything is logical - he is trying to switch - the status is already equal to the desired one - OK.
The only thing I can suggest to you is probably to look for an action that checks the value of the field BEFORE switching the process status (to fill it after switching and give an error when it is fired again and the value is present).
Maxim, I don’t really want to make crutch decisions (there are already so many additional fields that you can’t figure them out. We’ll think about it and write it off
08.04.2021, 17:52
Original comment available on version: ru
Please join the conversation. If you have something to say - please write a comment. You will need a mobile phone and an SMS code for identification to enter.
Log in and comment
Copyright © OneBox 2024
