This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice This article is not considered official documentation for K2 software and is provided “as is” with no warranties.
Certain users belonging in nested groups are not able to trigger Workflows, despite being granted start rights.
Some users belonging in nested groups don't have their process rights carried over:
"UserA" who is a member of "SubGroupA," is not able to start a process instance.
"SubGroupA" is a member of "MainGroup".
"MainGroup" has been granted with process start rights.
- Enable the Resolve Nested Group property from either K2 Workspace or K2 Management.
On K2 Workspace:
On the K2 Management site:
- Restart the K2 Blackpearl service.
- Run the script to expire the group:
SET [ExpireOn] = GETDATE(),
[Resolved] = 0,
[ContainerResolved] = 0,
[ContainersExpireOn] = GETDATE(),
[MembersResolved] = 0,
[MembersExpireOn] = GETDATE()
WHERE FQN = 'K2:DENALLIX\MainGroup'
- Run the UMUser Get Group Users SmartObject method from the SmartObject Service Tester and provide the name of the AD Group and the security label.