Provide insights to cause of source thresholds
Ramon Schouten
Currently, we can only see if a threshold is reached yes/no and what causes it; create/update/delete.
It would be a real help if we could also see who actually causes the create/update/delete.
That way we can first validate the data before we approve it.
Now we always have to approve first and can only then see the actual changes.
Especially when adjusting some settings in the source import it would be amazing to know this before approving the import. Because once we approve, the updates are already "triggered" and will be executed no matter the further changes to our source system. This causes (a lot of) unwanted actions, that could have otherwise been prevented.