When the account (projection) is in DISPUTED situation, it's not quite obvious why, i.e. what are the conflicting focus objects. This could be stored or computed when requested, and it could also help with manual decision.
- account has employeeNumber attribute which is used for correlation
- there are multiple users with the same employeeNumber (because of typo/error in data in midPoint)
- recon results will only show DISPUTED
- administrator has to know what should be searched in midPoint, in this case, employeeNumber of the value of the account employeeNumber
In case of more complex correlation expressions this can be even more challenging.