Hello! Please advise how you can configure the prohibition of changes in the process, if another manager is already working with the same process.
Is it possible to improve here?
Hello! Please advise how you can configure the prohibition of changes in the process, if another manager is already working with the same process. Is it possible to improve here?
Good afternoon. In theory, with a special block in the process, you can block any changes in the process until someone has opened the same process. This will happen until the second user leaves the page with the process. But there is a jamb here, the second user may not leave the portal and then block work with the process in general
Good afternoon. In theory, with a special block in the process, you can block any changes in the process until someone has opened the same process. This will happen until the second user leaves the page with the process. But there is a jamb here, the second user may not leave the portal and then block work with the process in general
anonymous hamster OneBox production wrote: But there is a jamb here, the second user may not leave the portal and then block work with the process in general
and is it possible to issue the ID of the contact that works with the process in the error? and will this logic take into account the restapi user?
[quote]
anonymous hamster
OneBox production wrote:
But there is a jamb here, the second user may not leave the portal and then block work with the process in general
[/quote]
and is it possible to issue the ID of the contact that works with the process in the error?
and will this logic take into account the restapi user?
1. Yes, id+fio will be better 2. Initially, I did not expect this, but in principle it can be done. But will you also make the rest api wait until the conditional employee closes the task? This is how all your work will be done
1. Yes, id+fio will be better
2. Initially, I did not expect this, but in principle it can be done. But will you also make the rest api wait until the conditional employee closes the task? This is how all your work will be done
anonymous hamster OneBox production wrote: 2. Initially, I did not expect this, but in principle it can be done. But will you also make the rest api wait until the conditional employee closes the task? This is how all your work will be done
we don't need to close the task, just close the tab
[quote]
anonymous hamster
OneBox production wrote:
2. Initially, I did not expect this, but in principle it can be done. But will you also make the rest api wait until the conditional employee closes the task? This is how all your work will be done
[/quote]
we don't need to close the task, just close the tab
to summarize: We make a block in the process. When the user goes to the page with the process (opens the process), the block remembers that the user went to the page and checks every X seconds whether he stayed on it or not. While the user remains on the page, we do not allow saving information about this process for other users and show the error "User #xx XX XX XX is already working with this process, try saving later". Is everything right? Is it necessary not to save it, or is it impossible to give it at all? The block will take 6 hours. Also, is it possible to cancel the blocking of the process if someone opened the page and does not close it, for example, for 5-10 minutes? In order not to block the process for all employees in such a case. Or let them "deal" with such a user?
to summarize:
We make a block in the process. When the user goes to the page with the process (opens the process), the block remembers that the user went to the page and checks every X seconds whether he stayed on it or not. While the user remains on the page, we do not allow saving information about this process for other users and show the error "User #xx XX XX XX is already working with this process, try saving later". Is everything right? Is it necessary not to save it, or is it impossible to give it at all?
The block will take 6 hours.
Also, is it possible to cancel the blocking of the process if someone opened the page and does not close it, for example, for 5-10 minutes? In order not to block the process for all employees in such a case. Or let them "deal" with such a user?
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
Donate
You don't have enough funds in your account Top up