Hide Forgot
Description of problem: I don't think that every role should have the possibility to abort any running process instance of another owner. I would leave this just for "admin", "analyst", and maybe "developer" roles according to this document https://bugzilla.redhat.com/attachment.cgi?id=795734 For "user" role I would forbid it. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create a user "user1" with role "admin". 2. Create a second user "user2" with role "user". 3. Log in to Business central as the user "user1". 4. As the user "user1" start any process definition with a human task just to be able to abort the process instance. 5. Log out and log in as the user "user2". 6. As the user "user2" abort the process instance the user "user1" started before. Actual results: Expected results: Additional info:
There is currently no user-specific access control on who is allowed to abort a process instance. Will have to defer this.
Lowering to medium as this looks to be an enhancement
Employee 'msalatin' has left the company.