The checkbox Available checks if all the process actions are available within a process flow. Now I have the challenge that I have different Table Tasks. Different roles for the table tasks but the processflow is the same for all of them. I want to keep it in one processflow but in order to have the process "available” they all need, in theorie, to have all the table tasks assigned to the role? Is it always necessary to have all the table tasks assigned to the role in order to have access to the processflow or is it possible to have the processflow available but not all the table tasks that trigger the processflow?
It is not desirable to have all table tasks available to all roles that access the processflow, but to be sure it will work for the roles it seems necessary. Thanks in advance.
Process Flow rights, checkbox Available - Different start table tasks
Why not use subflows for this?
Then all tasks can call the same subflow.
Flow 1: task A → subflow1
Flow 2: task B → subflow1
Flow 3: task C → subflow1
Then you can assign rights for role 1 to flow 1 + subflow 1.
That would also be my favourite solution except some of the actions needed in the flow are not supported by a subflow which makes it unfortunately not possible to make a convenient subflow for re-use. We have platform version 2025.3 and at the moment we cannot upgrade yet to a higher platform version. What I would get is an extended version of:
Flow 1: task A → subflow1 → Task/action they all need → subflow2 ..
Flow 2: task B → subflow1 → Task/action they all need → subflow2 ..
Flow 3: task C → subflow1 → Task/action they all need → subflow2 ..
One example is this one (Oauth user login). OAuth user login in Subflow | Thinkwise Community
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.