We have many workflows that do widely different tasks. A lot of them use
the User entity but need different attributes, especially some custom
auxiliary classes/attributes. I've often wondered what the best practice
is for Entities. Is it better to use one Entity with dozens of
attributes or several Entities with a smaller number of attributes, each
built around a particular task or pattern of attributes? We're not
experiencing any problems, I was just wondering what others do. I
currently only create separate entities if I have a need to limit search

stober's Profile: https://forums.netiq.com/member.php?userid=5986
View this thread: https://forums.netiq.com/showthread.php?t=50610