Is anyone else unable to run it or is it just our instance? (We're using the latest version) Build 4.0.60.5.1 (NB)
Is anyone else unable to run it or is it just our instance? (We're using the latest version) Build 4.0.60.5.1 (NB)
Is anyone else unable to run it or is it just our instance? (We're using the latest version) Build 4.0.60.5.1 (NB)
Is anyone else unable to run it or is it just our instance? (We're using the latest version) Build 4.0.60.5.1 (NB)
I'm wondering what the implications of removing the role tags from inactive user profiles is? By keeping these tags, inactive users still show up in the case worker and staff lists after they've left the agency which leads to very long staff/case worker lists. Do other communities automatically remove these tags when deactivating user accounts? Interested to hear thoughts and practices.
I'm wondering what the implications of removing the role tags from inactive user profiles is? By keeping these tags, inactive users still show up in the case worker and staff lists after they've left the agency which leads to very long staff/case worker lists. Do other communities automatically remove these tags when deactivating user accounts? Interested to hear thoughts and practices.
Okay yes you've brought to my attention what I'd consider to be a bug. It's because there is a Disconnect between User ActiveYN and People ActiveYN, so it's actually the Front Desk > People record for the User account that is controlling whether the User is showing up in those drop-down menus or not.
You could, theoretically, manually deactivate the People record. This is, I think, what's supposed to happen when you deactivate a User.
@Ali Ryder Thank you!
Comments