Add the ability to view the names of persons which cause a blocked import from a source system
M
Mark Spreeuwenberg
Once an import of a source system is blocked, I would like to see the persons that cause this. For example, when the import is blocked because to many persons were removed from the source, I would like to information of the persons. This helps a lot when I need to validate and approve the import.
Roel van de Kerkhof
This would be a great feature...
Tim Verlaek
We would like to have this functionality, it would help a lot
Wendy Bleker - Balhan
Today something is also going wrong in our environment. Last night according to the daily schedule, the import from our source system was started again, but ended in wanting to remove most of the employees. Fortunately we have a threshold on deleted persons and he did not implement the import. However, there is now no logging anywhere to see what is going on, what we need to solve first to ensure that the next import is successful. Would like to see in the snapshot what he wanted to remove.
A
Arjen Korpershoek
We would like to have this functionality too, it would help al lot.
R
Rick van den Dijssel
Merged in a post:
Deleted person view on blocked import
Arnout van der Vorst
When importing a source system, you can view the deleted persons when the snapshot has been created. However, when an import is blocked due to a threshold on the removal of persons, you cannot view which persons were actually missing from the import to cause the block. So the approve is a bit of a blind approve without knowing the exact impact.
R
Rick van den Dijssel
Merged in a post:
See what records are involved by a threshold approval
R
René de Jong
If you have a threshold approval at you source system. There is no easy way to see what record are involved.
I like to have a solution for that, so i do not have to call the holy whatever beforce i push that button.
Maybe the raw-data records can be green, white and red. Green will be added when published, Red will be deleted en white wil be the rest.
R
René de Jong
My new feedback could be another way to prevent a disaster: https://feedback.helloid.com/provisioning/p/allow-to-remove-snapshot-when-no-enforced-evaluation-was-done
Please Vote on this too.
S
Steve MIller
When showing clients HelloID provisioning, I always talk up the amount of visibility they have into the data and operations of the system. This would just add to it and help make provisioning better for everyone.