Data Quality Identifier Allocations
Allocated identifiers remain reserved even when their artifacts retire. Earlier acceptance numbers remain historical references and do not extend this module's sequences. Actor numbering belongs to the shared CRM register.
Series
| Identifier Series | Reserved Range | Next Available |
|---|---|---|
MOD-CRM-DQ | module identity | — |
FEAT-CRM-DQ- | 01 to 05 | 06 |
CON-CRM-DQ- | 001 to 005 | 006 |
ACT-CRM- | 006 to 008 reserved by Data Quality; earlier actor allocations belong to Entities | 009 |
CAP-CRM-DQ- | 001 to 019 | 020 |
JNY-CRM-DQ- | 001 to 006 | 007 |
ATS-CRM-DQ- | 001 to 019 (matching capability numbers) | 020 |
FND-CRM-DQ- | 001 to 053 | 054 |
OQ-CRM-DQ- | 001 to 006 | 007 |
DOM-CRM-DQ- | 001, 003, 004 (the number of the active Key Concept each realises; the retired concepts 002 and 005 have no object) | the next concept's number |
STATE-CRM-DQ- | 001 to 006 | 007 |
WF-CRM-DQ- | 001 to 009 | 010 |
SVC-CRM-DQ- | duplicates, merges (one per source module) | — |
SCR-CRM-DQ- | 001 to 011 | 012 |
ADR-CRM-DQ- | 001 to 019 | 020 |
IOP-CRM-DQ- | none allocated: the module asks no model a question | 001 |
Rows Inside Capabilities
| Artifact | Title | Rules (BR-…-NN) | Scenarios and edge cases (SC-…-NN) | Next free BR | Next free SC |
|---|---|---|---|---|---|
CAP-CRM-DQ-001 | Detect duplicate records after changes | 01 to 12 | 01 to 03 | 13 | 04 |
CAP-CRM-DQ-002 | Explain the strength of a duplicate suggestion | 01 to 13 | 01 to 02 | 14 | 03 |
CAP-CRM-DQ-003 | Set the response to duplicate matches | 01 to 12 | 01 to 02 | 13 | 03 |
CAP-CRM-DQ-004 | Check drafts and account for block overrides | 01 to 13 | 01 to 02 | 14 | 03 |
CAP-CRM-DQ-005 | Refresh duplicate evidence across a record type | 01 to 12 | 01 to 02 | 13 | 03 |
CAP-CRM-DQ-006 | Reuse a contact during portal registration | 01 to 11 | 01 to 02 | 12 | 03 |
CAP-CRM-DQ-007 | Review duplicate groups in a shared queue | 01 to 10 | 01 to 03 | 11 | 04 |
CAP-CRM-DQ-008 | Dismiss false matches and reopen review | 01 to 11 | 01 to 02 | 12 | 03 |
CAP-CRM-DQ-009 | Record a duplicate that matching missed | 01 to 06 | 01 to 02 | 07 | 03 |
CAP-CRM-DQ-010 | Review and merge from a record page | 01 to 08 | 01 to 02 | 09 | 03 |
CAP-CRM-DQ-011 | Understand the duplicate-review workload | 01 to 07 | 01 to 01 | 08 | 02 |
CAP-CRM-DQ-012 | Prepare a merge and choose its survivor | 01 to 12 | 01 to 03 | 13 | 04 |
CAP-CRM-DQ-013 | Resolve differences in the merge preview | 01 to 13 | 01 to 03 | 14 | 04 |
CAP-CRM-DQ-014 | Preserve the right information on the surviving contact | 01 to 14 | 01 to 03 | 15 | 04 |
CAP-CRM-DQ-015 | Keep related records consistent through a merge | 01 to 11 | 01 to 03 | 12 | 04 |
CAP-CRM-DQ-016 | Execute the approved merge atomically | 01 to 15 | 01 to 03 | 16 | 04 |
CAP-CRM-DQ-017 | Combine organizations and their connections safely | 01 to 10 | 01 to 03 | 11 | 04 |
CAP-CRM-DQ-018 | Resolve identities absorbed by a merge | 01 to 10 | 01 to 02 | 11 | 03 |
CAP-CRM-DQ-019 | Inspect merge outcomes and attribution | 01 to 11 | 01 to 02 | 12 | 03 |
Rows Inside Journeys
| Journey | Title | Assertions (AS-…-NN) | Next free AS |
|---|---|---|---|
JNY-CRM-DQ-001 | A reviewer settles duplicate work and revisits a dismissal | 01 to 03 | 04 |
JNY-CRM-DQ-002 | An administrator combines a sparse contact with a member record | 01 to 03 | 04 |
JNY-CRM-DQ-003 | An administrator renews approval after records change | 01 to 02 | 03 |
JNY-CRM-DQ-004 | An administrator unifies duplicate organizations | 01 to 02 | 03 |
JNY-CRM-DQ-005 | An administrator configures blocking and an accountable exception | 01 to 02 | 03 |
JNY-CRM-DQ-006 | A colleague follows an absorbed identity and inspects its history | 01 to 02 | 03 |
Rows Inside Acceptance Test Sets
| Set | Scope | Scenarios | Next free |
|---|---|---|---|
ATS-CRM-DQ-001 | Detect duplicate records after changes | 01 to 11 | 12 |
ATS-CRM-DQ-002 | Explain the strength of a duplicate suggestion | 01 to 09 | 10 |
ATS-CRM-DQ-003 | Set the response to duplicate matches | 01 to 09 | 10 |
ATS-CRM-DQ-004 | Check drafts and account for block overrides | 01 to 08 | 09 |
ATS-CRM-DQ-005 | Refresh duplicate evidence across a record type | 01 to 07 | 08 |
ATS-CRM-DQ-006 | Reuse a contact during portal registration | 01 to 06 | 07 |
ATS-CRM-DQ-007 | Review duplicate groups in a shared queue | 01 to 08 | 09 |
ATS-CRM-DQ-008 | Dismiss false matches and reopen review | 01 to 08 | 09 |
ATS-CRM-DQ-009 | Record a duplicate that matching missed | 01 to 04 | 05 |
ATS-CRM-DQ-010 | Review and merge from a record page | 01 to 06 | 07 |
ATS-CRM-DQ-011 | Understand the duplicate-review workload | 01 to 04 | 05 |
ATS-CRM-DQ-012 | Prepare a merge and choose its survivor | 01 to 07 | 08 |
ATS-CRM-DQ-013 | Resolve differences in the merge preview | 01 to 10 | 11 |
ATS-CRM-DQ-014 | Preserve the right information on the surviving contact | 01 to 14 | 15 |
ATS-CRM-DQ-015 | Keep related records consistent through a merge | 01 to 09 | 10 |
ATS-CRM-DQ-016 | Execute the approved merge atomically | 01 to 14 | 15 |
ATS-CRM-DQ-017 | Combine organizations and their connections safely | 01 to 09 | 10 |
ATS-CRM-DQ-018 | Resolve identities absorbed by a merge | 01 to 08 | 09 |
ATS-CRM-DQ-019 | Inspect merge outcomes and attribution | 01 to 07 | 08 |
Design Allocation
Allocated for the design layer draft of 2026-10-23, before any design file was written.
| Id | Title |
|---|---|
DOM-CRM-DQ-001 | Possible Duplicate |
DOM-CRM-DQ-003 | Merge Plan |
DOM-CRM-DQ-004 | Merge |
STATE-CRM-DQ-001 | Possible duplicate review standing |
STATE-CRM-DQ-002 | Duplicate group |
STATE-CRM-DQ-003 | Duplicate re-check run and its batches |
STATE-CRM-DQ-004 | Merge plan lifecycle |
STATE-CRM-DQ-005 | Merge attempt and its job |
STATE-CRM-DQ-006 | Absorbed identity |
WF-CRM-DQ-001 | Detect duplicates after a committed change |
WF-CRM-DQ-002 | Re-check every record of a type |
WF-CRM-DQ-003 | Check a draft and create past a block |
WF-CRM-DQ-004 | Decide about a pair or a group and regroup |
WF-CRM-DQ-005 | Prepare, refresh and change a merge plan |
WF-CRM-DQ-006 | Execute a merge |
WF-CRM-DQ-007 | Settle lost merge jobs and expire abandoned plans |
WF-CRM-DQ-008 | Offer and create a contact at portal sign-up |
WF-CRM-DQ-009 | Provision, export, reset and purge the module's data with the workspace |
SVC-CRM-DQ-duplicates | Duplicates service module |
SVC-CRM-DQ-merges | Merges service module |
SCR-CRM-DQ-001 | Data Quality overview |
SCR-CRM-DQ-002 | Duplicate review queue |
SCR-CRM-DQ-003 | Duplicate group |
SCR-CRM-DQ-004 | Dismissed duplicates |
SCR-CRM-DQ-005 | Recently merged |
SCR-CRM-DQ-006 | Merge details |
SCR-CRM-DQ-007 | Start a merge |
SCR-CRM-DQ-008 | Merge workspace |
SCR-CRM-DQ-009 | Duplicate rules configuration |
SCR-CRM-DQ-010 | Possible duplicates and Merge on a record page |
SCR-CRM-DQ-011 | Duplicate warning and block at record creation |
ADR-CRM-DQ-001 | Two service modules realise Data Quality; Entities keeps the records |
ADR-CRM-DQ-002 | Detection follows committed changes and never holds up a save |
ADR-CRM-DQ-003 | Detection is deterministic and asks no model |
ADR-CRM-DQ-004 | A block acts at creation; an exception commits with the record it lets through |
ADR-CRM-DQ-005 | A merge is one all-or-nothing transaction with no compensation |
ADR-CRM-DQ-006 | Other applications change their own rows inside the merge |
ADR-CRM-DQ-007 | Approval binds to the material plan last shown |
ADR-CRM-DQ-008 | A merge runs as a durable job with one working task |
ADR-CRM-DQ-009 | Absorbed identities answer gone, point at a live survivor and are never reused |
ADR-CRM-DQ-010 | Merge records keep the originals for the life of the workspace |
ADR-CRM-DQ-011 | Portal logins: relink one, block two |
ADR-CRM-DQ-012 | The survivor is written through its owner's ordinary save |
ADR-CRM-DQ-013 | A merge stays one transaction up to a ceiling |
ADR-CRM-DQ-014 | Re-checks follow the queued-work standard |
ADR-CRM-DQ-015 | Duplicate groups are stored components with a stable identity |
ADR-CRM-DQ-016 | Data Quality records carry no custom fields |
ADR-CRM-DQ-017 | No Data Quality operation is published to Submissions |
ADR-CRM-DQ-018 | Merge plans are shared working state that expires |
ADR-CRM-DQ-019 | Portal sign-up reuses contacts through CRM-owned functions |
FND-CRM-DQ-035 to FND-CRM-DQ-042 | Design findings |
OQ-CRM-DQ-006 | Design open question |
INV-DOM-CRM-DQ-<NNN>-NN | Invariants are rows inside their Domain Object, numbered from 01 per object |
Independent Design Examination Allocations
| Id | Examination Concern |
|---|---|
FND-CRM-DQ-043 | Missing design brief |
FND-CRM-DQ-044 | Decision-preserving rescoring |
FND-CRM-DQ-045 | Detection transaction boundary |
FND-CRM-DQ-046 | Rolled-back merge visibility and retries |
FND-CRM-DQ-047 | Screen behavior and pattern evidence |
FND-CRM-DQ-048 | Invariant enforcement and source strength |
FND-CRM-DQ-049 | Merge persistence ownership wording |
FND-CRM-DQ-050 | Re-check windows are read at processing time |
FND-CRM-DQ-051 | External orchestration claims lack pinned evidence |
Control Backfill Allocations
| Id | Purpose |
|---|---|
FND-CRM-DQ-052 | The service-wide internal-use classification does not identify the personal class of duplicate evidence and merge snapshots containing people’s original and resulting values. |
FND-CRM-DQ-053 | Restoring a duplicate pair clears the earlier dismissal actor, time and explanation in the mutable candidate; the examined path retains only the new modification stamp rather than append-only history of both decisions. |