Repository navigation
Document tolerant matching, matching confidence and the profile match review queue - #6382
Draft
VivekVinushanth wants to merge 1 commit into
Draft
VivekVinushanth wants to merge 1 commit into
VivekVinushanth wants to merge 1 commit into
Conversation
Contributor
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true
Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Documents tolerant matching, the matching confidence settings and the profile match review queue for the Customer Data Service.
The existing Unification rules concept page describes the behaviour before these were added, and is now wrong in one respect: it says evaluation stops at the first matching rule and that only one rule fires per run. Every active rule is now evaluated for each candidate pair, and the rest may object to the one that agrees.
What changed
Updated
concepts/unification-rules.md— adds the attribute kind and the exact/tolerant choice to the rule structure, explains what each kind is worth on agreement and on disagreement, and replaces the first-match-wins description with how the decision is actually reached.guides/manage-unification-rules.md— the two new fields in the create-rule steps.New
guides/configure-matching-confidence.md— the automatic unification and review scores, and the "an exact match is final" setting.guides/review-profile-matches.md— working the review queue, what Merge and Reject do, and what a rejection remembers.Both new pages follow the existing pattern: content in
en/includes/, an Asgardeo stub inen/asgardeo/docs/, plus nav entries inen/asgardeo/mkdocs.yml.Wording follows the console labels so the docs read the same as the screen — "What this attribute holds", "How it is matched", "Exact" / "Tolerant", "Unify profiles automatically", "An exact match is final".
Not included
Screenshots. The existing pages carry them for the rule list and create form, and the new pages should get the same treatment for the review queue and settings once the feature is available to capture against.
Blocked on
The server-side support is still open — wso2/identity-customer-data-service#307. This should not merge before a Customer Data Service release containing it, or the docs describe a feature that is not yet available.