Few years ago, when external consultants helped our company with ServiceNow (Jakarta version) implementation, they advised that Nested Groups concept didn't work well. I am wondering if that's the case or/and something has changed in more recent versions
We use nested groups at our current customer. What we have done is have separate groups for security and assignment. For assignment we use the organizational structure with the nested groups as you describe. This works well for our purpose. Sounds like it would fit yours as well.
Can you share the concerns the consultants expressed?
Is there any other way to use nested grouping for reporting purposes only (without assigning the roles). In ideal scenario, I'd like to be able to run the timecard summary report on any org level (managers level, teamleads level, developers level)
We use nested groups at our current customer. What we have done is have separate groups for security and assignment. For assignment we use the organizational structure with the nested groups as you describe. This works well for our purpose. Sounds like it would fit yours as well.
Can you share the concerns the consultants expressed?
Honestly, I don't remember exactly. It was around 3 years ago, when we just implemented SNOW. No one internally had that knowledge, so we had to rely on their advice. It looks like the segregation security and assignment groups will work. Thank you
