What is a one sentence summary of your feature request?
Allow HomonymEntityLink to filter out archived identities so that they are not flagged as potential duplicates during identity creation.
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
When creating a new identity, the homonymy check currently returns archived identities (state = ARC) as potential duplicates, which is misleading for end users who interpret this as a conflict with an active account.
The expected behavior is that archived identities should be excluded from the homonymy results, as they no longer represent active users in the organization.
The best solution would be to support filtering on the identity’s state (or record state) directly within the HomonymEntityLink configuration — for example, via a Property filter on MainRecord.State.Code with an Expression or Value comparator. This is consistent with how other aspects handle state-based conditions in the XML configuration.
We attempted three approaches based on the documentation but all failed due to current platform limitations: Value attribute not supported, multi-level navigation properties not supported, and simultaneous use of ComparisonProperty + Expression not allowed.
How do you currently solve the challenges you have by not having this feature?
We have no workaround at this time. Users must manually ignore the warning and proceed with the creation, which creates confusion and increases the risk of unnecessary escalations or abandoned workflows. We added an informational note in our user guide to explain the behavior, but this is not a satisfactory long-term solution.