All Call Activities appear in the Start Process dialog by default, just as for a normal process. However the use case of a Call Activity is to have a self contained sub-process. Surely such a sub-process is not necessarily a standalone executable and should only be executed by it’s parent supra-process. So how can I define / prevent it from appearing in the Start Process list?
I tried deselecting the Executable checkbox in modeler, but then the supra-process throws an error : no processes deployed with key ‘CallActivity1’
Any thoughts on this?
Update:
Changing the Admin Permissions on the supra-process and sub-process (Call Activity) does affect whether it appears in the Start Process list. However it also affects whether the diagram is displayed or not.
Surely there must be a way of not including a Call Activity in the Start Process list but still show the diagram?
I believe what you are after are authorisations [1].
For a process to be visible in the start drop-down, the user principle will likely need read process definition and start process instance permissions. You can set authorisations via the admin console. Have a go, however in my experience, there’s a bit of a learning curve…
Yip you’re right regarding granting the correct authorizations on the Process Instance (Call Ativity).
If I do not grant READ permissions on the Call Activity then it does not appear in the Start List. Precisely what I want. However, it also causes the diagram from not being visible when a user task is part of that sub-process (Call Activity).
The workaround I’m using currently is to grant READ permissions on the process instance but no CREATE_INSTANCE permissions. This allows the diagram to be displayed and the process to appear in the Start list but without the permissions to be instantiated. The rather pathetic consequence of this is that my Start list is cluttered with processes which should not be listed, which upon clicking and after the business key being provided and Start clicked, informs you that it cannot be started.
As an interim, I guess you could remove the start instance capability in tasklist (see [1] it works for tasklist with the right plugin point names). Then add your own tasklist plugin to start process instance if required…