Skip to content

MID-10415 Fix mapping property autocomplete matching#668

Open
kay1313 wants to merge 1 commit into
masterfrom
fix/MID-10415
Open

MID-10415 Fix mapping property autocomplete matching#668
kay1313 wants to merge 1 commit into
masterfrom
fix/MID-10415

Conversation

@kay1313
Copy link
Copy Markdown
Contributor

@kay1313 kay1313 commented May 25, 2026

Summary

Fixed autocomplete filtering for focus object item paths used in mapping-related GUI fields.

Previously, the provider used prefix-only matching. Because of that, typing name in the resource wizard inbound mapping MidPoint property field proposed only name, but did not propose other valid properties that contain the same text, such as familyName or givenName.

The filtering now uses partial matching, so matching properties are suggested even when the typed text appears later in the property name. Matching is also case-insensitive.

Affected areas

The changed provider is FocusDefinitionsMappingProvider. It is used by focus object property/item-path autocomplete fields in mapping and correlation screens.

This affects suggestion filtering in places such as:

  • resource wizard mapping tables:
    • inbound mapping target / MidPoint property
    • outbound mapping source
    • activation and credentials mapping source/target fields
    • smart mapping table source/target fields
  • resource association wizard mapping tables:
    • association mapping source/target fields
    • association attribute mapping fields
  • focus, role, and object template mapping tables:
    • focus mapping source fields
    • focus mapping target fields
    • role wizard focus mapping source fields
  • correlation item reference autocomplete fields

The change only affects autocomplete suggestions for focus object properties/item paths. It does not change mapping evaluation, resource schema handling, repository queries, or resource attribute autocomplete. The resource attribute selector already used partial case-insensitive filtering through a different provider.

Resource wizard mapping property autocomplete used prefix-only and
case-sensitive filtering. This meant that typing "name" found only
"name", not "familyName" or "givenName", and typing "Name" found no
matches.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant