Send notification on update event
complete
R
Rick van den Dijssel
complete
R
Rick van den Dijssel
in progress
R
Rick van den Dijssel
Moved to September release because of a delay in June
R
Rick van den Dijssel
planned
Planned August Release
R
Rick van den Dijssel
under review
R
Rick van den Dijssel
Merged in a post:
Name change notifications and processing
J
John Zaharakis
Many of our clients request an email notification prior to a name change. In some instances the name change will be process automatically X days after the notification. It would be useful if there was a way to natively configure this within the a target system configuration.
G
Grady Koopman
John Zaharakis
At the moment we can suggest to add a generic update event as new notification type, right now we dont have the functionality to detect any changes upfront before they arrive in our HelloID Vault database.
J
John Zaharakis
Grady Koopman: Thank you for the response. We are not looking for the notification before the changes arrive in the HelloID Vault database. We are looking for HelloID to detect the change when it occurs, send an email notification that a name change has been detected, and then change the sAMAccountname or userPrincipalName X days after the notification is sent. This is often requested by our customers as they don't want the end users logon name to change immediately causing a support call when they can't log in.
G
Grady Koopman
John Zaharakis:
From the HelloID point of view we don’t use process based update’s like (transfer, change names, change manager, etc…) anymore. Within HelloID provisioning we only have the generic update call being triggered at the moment the update occurs. This means you can send a specific configured mail notification on the account update event, but not having it based on a specific set of attributes.
In basics we always advice our customers to not change the sAMAccountName attribute automatically in case of a name change, by default we always calculate this attribute being based on the employees birth naming convention.
HelloID could send an email to the employee asking them to contact the service desk in case they want to have their account logon name being changed. From HelloID we don’t support update for the sAMAccountName attribute as well.
We also wouldn’t implement functionality to delay the update calls at the moment, because there is only one update call for each employee update action. Having a delay in this means the other attributes will also have to wait before being updated.
J
John Zaharakis
Grady Koopman: Thank you again for the response. Makes sense and we will handle accordingly.