--- id: FAS-CRM-DQ-03 feature: FEAT-CRM-DQ-03 product_area: crm module: data-quality revision: 1 status: proposed product_intent: proposed source_sha: services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f rhythm-v2-docs: 61315bb0538e230286687677da2b04b1d33f162b capabilities: - CAP-CRM-DQ-012 - CAP-CRM-DQ-013 - CAP-CRM-DQ-014 - CAP-CRM-DQ-015 scenarios: - id: FAS-CRM-DQ-03-01 title: A selected survivor leads to reviewable choices kind: behaviour exercises: - CAP-CRM-DQ-012 - CAP-CRM-DQ-013 relies_on: - ATS-CRM-DQ-012-04 - ATS-CRM-DQ-013-01 preconditions: Two compatible run-owned contacts disagree on a retained scalar field. steps: >- Create the plan, override its survivor and inspect the resulting questions. expected: >- The chosen survivor remains selected and the preview exposes the relevant differences. negative: false data_needs: >- Use an isolated workspace, run-owned records and the permission personas described by the scenario. Failures and changed dependent records must be supplied by fixtures owned by the run. bound_to: [] provenance: proposed source: ATS-CRM-DQ-012-04; ATS-CRM-DQ-013-01 execution_gap: FND-CRM-DQ-072 note: >- The capability assertions define the component evidence. No executable binding is claimed for this complete feature sequence. - id: FAS-CRM-DQ-03-02 title: Collection choices and consent form one preview kind: interaction exercises: - CAP-CRM-DQ-013 - CAP-CRM-DQ-014 - CAP-CRM-DQ-015 relies_on: - ATS-CRM-DQ-013-04 - ATS-CRM-DQ-014-01 - ATS-CRM-DQ-014-03 - ATS-CRM-DQ-015-03 preconditions: >- Contacts have competing e-mail choices, different consent values and overlapping activity links. steps: >- Review scalar and collection decisions, choose retained values and recompute the preview. expected: >- The resolved preview follows the cited checks for consent, communication slots and related links. negative: false data_needs: >- Use an isolated workspace, run-owned records and the permission personas described by the scenario. Failures and changed dependent records must be supplied by fixtures owned by the run. bound_to: [] provenance: proposed source: ATS-CRM-DQ-013-04; ATS-CRM-DQ-014-01; ATS-CRM-DQ-014-03; ATS-CRM-DQ-015-03 execution_gap: FND-CRM-DQ-072 note: >- The capability assertions define the component evidence. No executable binding is claimed for this complete feature sequence. - id: FAS-CRM-DQ-03-03 title: Participant changes discard only inapplicable decisions kind: lifecycle exercises: - CAP-CRM-DQ-012 - CAP-CRM-DQ-013 relies_on: - ATS-CRM-DQ-012-05 - ATS-CRM-DQ-013-18 preconditions: A reviewed working plan contains valid saved decisions. steps: >- Change the participant set, then answer a remaining question and read the preview again. expected: >- Applicable decisions survive and answers belonging to removed participants do not remain effective. negative: false data_needs: >- Use an isolated workspace, run-owned records and the permission personas described by the scenario. Failures and changed dependent records must be supplied by fixtures owned by the run. bound_to: [] provenance: proposed source: ATS-CRM-DQ-012-05; ATS-CRM-DQ-013-18 execution_gap: FND-CRM-DQ-072 note: >- The capability assertions define the component evidence. No executable binding is claimed for this complete feature sequence. - id: FAS-CRM-DQ-03-04 title: Type-specific read and merge keys guard planning kind: permission exercises: - CAP-CRM-DQ-012 relies_on: - ATS-CRM-DQ-012-02 - ATS-CRM-DQ-012-16 preconditions: Contact-only and organization-only personas have distinct permission sets. steps: >- Attempt planning for both types and compare the permitted and refused requests. expected: >- A persona can prepare only the type for which it holds the full required permission pair. negative: true data_needs: >- Use an isolated workspace, run-owned records and the permission personas described by the scenario. Failures and changed dependent records must be supplied by fixtures owned by the run. bound_to: [] provenance: proposed source: ATS-CRM-DQ-012-02; ATS-CRM-DQ-012-16 execution_gap: FND-CRM-DQ-072 note: >- The capability assertions define the component evidence. No executable binding is claimed for this complete feature sequence. - id: FAS-CRM-DQ-03-05 title: Changing dependent work invalidates earlier approval kind: regression exercises: - CAP-CRM-DQ-013 - CAP-CRM-DQ-016 relies_on: - ATS-CRM-DQ-013-07 - ATS-CRM-DQ-016-02 preconditions: >- A ready preview has been shown before a dependent task or chosen source value changes. steps: >- Keep the earlier approval material, change the dependent record, submit that earlier approval and then refresh the preview. expected: >- The earlier approval is refused; the new preview makes the changed material available for renewed review. negative: false data_needs: >- Use an isolated workspace, run-owned records and the permission personas described by the scenario. Failures and changed dependent records must be supplied by fixtures owned by the run. bound_to: [] provenance: proposed source: ATS-CRM-DQ-013-07; ATS-CRM-DQ-016-02 execution_gap: FND-CRM-DQ-072 note: >- The capability assertions define the component evidence. No executable binding is claimed for this complete feature sequence. evidence: - provenance: documented source: FEAT-CRM-DQ-03 - provenance: proposed source: - ATS-CRM-DQ-012-04 - ATS-CRM-DQ-013-01 - ATS-CRM-DQ-013-04 - ATS-CRM-DQ-014-01 - ATS-CRM-DQ-014-03 - ATS-CRM-DQ-015-03 - ATS-CRM-DQ-012-05 - ATS-CRM-DQ-013-18 - ATS-CRM-DQ-012-02 - ATS-CRM-DQ-012-16 - ATS-CRM-DQ-013-07 - ATS-CRM-DQ-016-02 --- # Prepare a Reviewed Merge: Feature Acceptance Suite ## What the Feature Must Do as a Whole A merge preview must let an administrator settle differences before execution. Survivor selection, retained communication details and participant effects must describe one consistent proposed result. ## Interactions Between Capabilities Changing participants can invalidate decisions; changing source values or dependent work can invalidate approval. The suite checks these handoffs while retaining consent and participant safeguards. Every sequence remains proposed until one executable selection asserts its full outcome. Existing capability assertions supply evidence for parts of the sequence. ## Regression Record | Revision | Change | Scenario | Why | |---|---|---|---| | 1 | initial | all | Establish feature-level handoffs from the landed capability checks. |