Unable to assign in progress task instance of workflow waiting for approval to any user as users not getting populated.
Where candidate group is “flowable:candidateGroups=“internal/role/manager”” set and this role is having active users as members.
Hi asjadhav,
I have noticed a similar issue reported within our support organization that may be related to the one you described here. Although I am not entirely sure if it is the same project or your organization, I have contacted the engineer regarding the issue. Once the solution is identified, we will share our findings and resolution here in your post as well to benefit the community and assist others facing a similar problem.
Many thanks,
Sheila
Hi asjadhav,
That candidateGroup /internal/role/manager is the same one that’s used in the sample provisioning-with-workflow.
In the sample, the role is created in such a way that the role _id is manager.
If you were to create a role in the UI, then it wouldn’t have manager as the _id.
Instead, you’d have a unique _id and that’s the value that you’ll need to use in your workflow.
Hope that helps,
Amy
1 Like
Hi Amy,
As you mention its taking _id instead of name in /internal/role/manager but in real time the UI does not allow to define _id while creating the Internal Role .
Can you consider it as bug? For each environment the _id is going to different and modify workflow to hard coding the long numeric value is not a feasible solution
Hi Jayark,
Thank you for bringing this to our attention.
Could we kindly ask you to raise a support ticket detailing the problem you’re encountering.
If you suspect a bug, we recommend raising a support ticket for assistance. This not only allows you to report the issue but also enables you to track its progress through the Issue Tracker in Backstage.
You can find more information in the following Knowledge article: ForgeRock Issue Tracker
Best regards,
Sheila