Person aggregation with approval
complete
R
Rick van den Dijssel
We would like to automatically detect if a new person should be aggregated with an already existing person for a single or multiple source systems. To be on the safe side we want an approval of the system administrator before the persons are merged.
We provide the following solution:
- Add a fixed field “aggregation“ to the person mapping/model
- The administrator could use a single field map (single field aggregation or complex mapping (multiple field aggregation)
- This field is used to match and identify a unique person over multiple source systems or in a single source system
- Match the value of the field aggregation of new persons against existing and other new persons
- Use a matching algorithm that deducts a score based on the changes it takes to transform the aggregation value of the new person to the value of the already existing person list.
- If the score is higher than x we block the import of the new person for the reason that we suspect it isn’t a unique person.
- Allow the administrator to define the x in the previous statement
- An email is sent when a person is blocked
- Allow the administrator to merge or not merge (create person) on a blocked person with the reason we think we found a not unique person
Logan Hawker
Could we get an option to automatically aggregate users with the same ExternalID?
R
Rick van den Dijssel
Logan Hawker: The ability to automatically aggregate persons will be in HelloID in the near future. It's not yet planned but it will be soon. Please be aware that a ThenExternalID never should be the same for two persons (we will just import a single person). The trick here is to map a unique value for the ExternalID so that every person gets a unique value. Then use the previously mapped field as an aggregation field so the persons will be merged (now only manual with suggestions in the future automatically).
R
Rick van den Dijssel
complete
R
Rick van den Dijssel
in progress
R
Rick van den Dijssel
planned
Moved to April release due to a delay in session management in December
R
Rick van den Dijssel
under review
R
Rick van den Dijssel
planned
Planned March release
R
Rick van den Dijssel
under review