Dynamic Group rebuild are "polluting" user Change History

Question

Hi All, 
 I've been searching around the forum and can't find an answer to my question. Perhaps others are not experiencing this or don't see it as an issue. 
 We have users that are in a few (large) dynamic groups. Whenever a group is automatically rebuilt which is often, users' Change History is full of the changes and it's really difficult to find details on anything else that happened to the account. 
 I've been looking for a way to exclude the Dynamic Groups from Change Tracking, but so far I have not been able to do this. 
 Is this possible? If not, does anyone have any suggestions how we could work around it? 
 
 Thanks,

Terrance.Crombie · Answer

With Dynamic Groups that reference only native Virtual Attributes, it is possible to create a dedicated Active Roles configuration to handle real-time Dynamic Group operations. This has a few advantages: mainly, it frees up resources in your primary Active Roles configuration for other operations, but it also removes Dynamic Group operations from the logging of your primary Active Roles configuration. 
 When using Dynamic Groups that reference Active Roles Virtual Attributes, this becomes a little bit more complicated. You'd have to import your Virtual Attributes into the new configuration and then set up something like an Active Roles Synchronization Service Workflow to keep them in sync between the configurations. Still might be a good idea if you are interested in improving performance or simplifying logging. 
 I've also had some customers configure a dedicated service account on a Dynamic Group job server within the same configuration, and then filter out operations made by that account in their auditing tools. This might be a simpler ask depending on your needs. 
 We are aware that the current logging needs to be improved and we are tracking a requested change to this specific product functionality under ER 431618.

Dynamic Group rebuild are "polluting" user Change History

Top Replies