In the results I’m getting some identities that I was not expecting:
Identities that are no longer a Manager, but still have the managerStatus = “true”;
Identities that are a Manager to Inactive Identities
Is there a way to exclude these cases using the filters?
A solution I found was to have a daily task update the membership of the workgroup. It would apply the filters above, iterate over the results and manually remove the managers that match the exceptions. Would this be a good approach?
Before performing advance search with above filter, try running refresh task with below option
Having said that, the approach you mentioned for keeping the workgroup up to date with the active manager is effective. To make this work, you’ll need to schedule the rule runner task.
Additionally, you could consider using the Population (GroupDefinition) option, which automatically keeps the members updated. However, note that unlike the Workgroup, you cannot assign capabilities to a Population.
That is exactly the situation I have. There is a Population defined by the filter above to automatically manage the membership, but there are some identities that I wasn’t expecting to be included.
Refreshing the identities solved the situation where identities are no longer a manager. I actually had to add the option “noCheckPendingWorkflow” for some identities to be refreshed, but after that some of the wrongly displayed identities were solved.
For Identities that are a Manager to an Inactive identity, it still comes as a result of that filter. Is there a filter that could be applied to ensure that the subordinates are not inactive?
Okay got it. If you want to exclude managers with inactive subordinates, then as you mentioned you can go with a rule. Alternately, you can wipe off the manager details from inactive users.
