Hard limit of 10 Org Groups that can be discovered in Workflow Get nodes (per Type)?

[Berto2002]

We use this node quote a lot to discover what Organisation (organization) groups a user is in when they leave, so we can trigger removal requests and remove them.

The nodes returns results for up to 10 instances of the given group type; in the case above, this was "General".

We often paste this on the timeline for service desk visibility thus:

We use Org Groups for Subscribers to individual Services (applications) and the workflows add and remove users to these OGs each time the app team action create or remove a user.

I want to expand this facility but can you guess the issue? That's right, it won't be long before our users are members of more than 10 OGs of Type General. And then the workflow nodes will only 'Get' the first 10 and then we won't be able to act upon all their apps when they leave.

So I think I am highlighting what looks like a hard-coded limitation that is going to stop us expanding the use of our 'automated' subscriber list management system. And this, in itself, holds us back trying to make the portal easier for everyone by only showing the Services (apps) they have access to.

Yes, we have other OG types that could give 10+10+ etc but that means spreading my workflows for this activity across the types which will be confusing to manage and won't guarantee the issue won't occur because any given user may end up with the exact spread of 11+ apps that are in any given type.

I mentioned this in the HUG23 to Dave in TS but I don't know Dave's handle on there to alert him.

Can I please request a review and to get back to me on what we can do here to rectify or me workaround this limitation?

Thanks,

Rob

[Steve Giller]

After the node:

• Check that there are Groups populated - if so:
• Remove them from each group
• If Org Group 10 is populated, branch back to the Get User Groups node

That way nothing will happen if they aren't in a group, it will loop around as many times as necessary to remove all groups, and if they have exactly 10/20 etc. it will loop back but not try to remove number 11/21 etc.

[Berto2002]

That would help in the Leaver case, certainly. I will have a think through that idea.

But it's a 'destructive' approach so could not be used in any case where membership of the groups is still required.

[Berto2002]

Had a look at this and we also search for the applications a user is in when we have a Mover ticket; and we cannot allow this to be destructive as they are not leaving. So this is now the use case we have no workaround for (other than planning to ensure we have no more than 10 apps configured for any given OG type.

[Steve Giller]

I would suspect that it's simply not practical to return a potentially infinite number of Groups in a Workflow node.

This goal would probably be better achieved using the userGetGroupList API