Conditional Attribute updates for AD/Azure
Mike Sheldon
It would be beneficial if the an attribute could have conditions on whether an update should occur.
For example, if in a Active Directory target system with update attribute for mail, samaccountname, and upn is enabled. An account update is triggered, but the first/last names have not changed. The username generation should not process.
One of the issues right now is the following:
John Doe is the person with a username of jodoe because jdoe was taken at the time the account was created. After a period of time jdoe ends up being created and John Doe goes through an Account update. Their username would then be changed to jdoe now because that is the first iteration available.
If we only updating when first/last changes then this would not occur.
R
Rick van den Dijssel
Merged in a post:
Decrease updates on target systems
J
Jeroen ten Broek
We have currently 2 source systems. A HR system and a duty roster program. Because we have al lot of changes in the duty roster program (we have a lot of flexible employees, that work on diverent departments). Everyday there are lots of unnecessary updates for all targetsystems. It is not necessary that all systems needs to be updated.
Because of this load, we get serveral memory errors (e.g. powershell memory overload, HR systems time outs)
Can you investigate how to decrease the updates on target systems? For example our HR systems does not need to be updated for a change in the duty roster.
Jonathan Butler
We would welcome this change in HelloID. In our situation this is the problem we have seen when any source data changes at semesters end and triggers an audit of every account. What we end up with the is first username iteration now available b/c an older account was removed the users now get that address and an alias in Google for the old taking up 2 email addresses per account. So any account with a now available first iteration is updated regardless of an actual name change in the SIS source data.
R
Rick van den Dijssel
Merged in a post:
E-mail fields are case-sensitive
A
Aico Hoekman
We noticed that an update event is triggered when the e-mail address of a person or a manager changes from lowercase to uppercase and vice versa. Seeing that e-mail addresses are not case-sensitive an update event is not necessary in my opinion.
R
Rick van den Dijssel
Aico Hoekman merged this with conditional update because you want to have rules based on if an update should trigger yes or no.
Logan Hawker
This is the main issue that comes up for us with HelloID, usernames drop down to the lowest iteration if available during an account update.