The Camunda 8 docs lists candidateGroups as one of the mechanisms of assigment.
I would like to define a candidate group “managers” at organisation level, not only locally in one process specification. Where can I do that?
The Camunda 8 docs lists candidateGroups as one of the mechanisms of assigment.
I would like to define a candidate group “managers” at organisation level, not only locally in one process specification. Where can I do that?
Hi @ahense - currently you define it as a hard-coded string or FEEL expression in that process. I think this is an interesting idea and would love to share it with the product team. How do you envision it working? Do you think there should be a separate “Candidate Groups” management page in Console? Perhaps the ability to add a custom role to users?
Hi @nathan.loding - thank you I will try this for my experiments.
I am glad that you like the idea but it’s not mine. In general the organisational data like roles, positions, org group, capabilities etc. are stored at the level of the workflow engine and are shared by all workflow specifications on that engine. In the case of Camunda this would be under Organization/Organization management/Users. What is currently called roles there are priviledges vis-a-vis the workflow management system. What could be stored there as well are custom roles that are in relation with their roles in “real life”. These roles in real life have even a larger scope. So some systems even allow you to connect this part of the workflow management system to an Active Directory or LDAP.
Hi @ahense - I spoke with our Human Task Orchestration team, and they are looking to bring this feature to our SaaS product with the 8.5 release later this year! It’s still in development, so that release target may change, but the good is that it is in development!
I also - somewhat embarrassingly - missed that the 8.4 release already has this featured enabled, but only for Self-Managed. So if you are using Self-Managed with Identity, you can create groups and use that group in the list of candidateGroups. The implementation is different and more complex with SaaS, which is why it is coming in a future release.
Thanks @nathan.loding - that’s really good news.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.