--- id: FAS-PFM-CSH-02 title: Finding work through navigation acceptance feature: FEAT-PFM-CSH-02 product_area: platform module: console-shell revision: 1 status: proposed product_intent: proposed source_sha: rhythm-v2-docs: 25e253cb434aac6603ee294e3ca197ab6c4bfd0b react-console: baf6dae382d6f41dce976c7f848667ccc37e076f services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1 capabilities: - CAP-PFM-CSH-006 - CAP-PFM-CSH-007 - CAP-PFM-CSH-008 scenarios: - id: FAS-PFM-CSH-02-01 title: Administrative navigation identifies the direct destination kind: behaviour exercises: - CAP-PFM-CSH-006 - CAP-PFM-CSH-007 relies_on: - ATS-PFM-CSH-009-09 - ATS-PFM-CSH-006-05 preconditions: A customer administrator can reach Configuration Regions. steps: >- Open Regions directly and compare the sidebar link, active entry and breadcrumb. expected: >- The sidebar and breadcrumb agree on Regions within Configuration and the link uses its canonical workspace destination. negative: false data_needs: >- An isolated browser context and run-owned association fixtures; deterministic authority, response and clock variants where specified. bound_to: - TST-PFM-CSH-014 test_sources: - >- react-console:e2e/mock/url-architecture.mock.spec.ts#Configuration › CRM › Regions loads with its place in the sidebar and the breadcrumb provenance: test source: >- react-console:e2e/mock/url-architecture.mock.spec.ts#Configuration › CRM › Regions loads with its place in the sidebar and the breadcrumb action_evidence: provenance: test source: >- react-console:e2e/mock/url-architecture.mock.spec.ts#Configuration › CRM › Regions loads with its place in the sidebar and the breadcrumb assertion_evidence: provenance: test source: >- react-console:e2e/mock/url-architecture.mock.spec.ts#Configuration › CRM › Regions loads with its place in the sidebar and the breadcrumb - id: FAS-PFM-CSH-02-02 title: A placement gives an otherwise unfinished domain useful work kind: interaction exercises: - CAP-PFM-CSH-006 - CAP-PFM-CSH-008 relies_on: - ATS-PFM-CSH-006-11 preconditions: >- Awards is wholly planned and an active readable Prizes type is placed there. steps: >- Merge placements into the complete domain registry, apply visibility selection and compare with no placement. expected: >- Awards is retained with Prizes appended only in the placed variant, without rearranging built-in entries. negative: false data_needs: >- An isolated browser context and run-owned association fixtures; deterministic authority, response and clock variants where specified. bound_to: - TST-PFM-CSH-024 test_sources: - >- react-console:lib/custom-objects/__tests__/navigation.test.ts#keeps a hidden domain reachable when a custom object is placed under it - >- react-console:lib/custom-objects/__tests__/navigation.test.ts#appends to an existing app after its built-in items provenance: test source: >- react-console:lib/custom-objects/__tests__/navigation.test.ts#keeps a hidden domain reachable when a custom object is placed under it action_evidence: provenance: test source: >- react-console:lib/custom-objects/__tests__/navigation.test.ts#keeps a hidden domain reachable when a custom object is placed under it assertion_evidence: provenance: test source: >- react-console:lib/custom-objects/__tests__/navigation.test.ts#keeps a hidden domain reachable when a custom object is placed under it - id: FAS-PFM-CSH-02-03 title: An administrator returns from settings to the record being worked kind: lifecycle exercises: - CAP-PFM-CSH-006 - CAP-PFM-CSH-007 relies_on: - ATS-PFM-CSH-007-02 - ATS-PFM-CSH-006-05 preconditions: A contact record is open before entering Configuration. steps: >- Use the account menu to enter Configuration, visit Regions and select Back to app. expected: >- Settings replace daily navigation and departure restores the original contact destination and its navigation position. negative: false data_needs: >- An isolated browser context and run-owned association fixtures; deterministic authority, response and clock variants where specified. bound_to: [] test_sources: [] provenance: proposed source: >- rhythm-v2-docs:specs/platform/console-shell/planning/features/FEAT-PFM-CSH-02-the-navigation-menu.md action_evidence: provenance: proposed source: >- rhythm-v2-docs:specs/platform/console-shell/planning/features/FEAT-PFM-CSH-02-the-navigation-menu.md assertion_evidence: provenance: proposed source: >- rhythm-v2-docs:specs/platform/console-shell/planning/features/FEAT-PFM-CSH-02-the-navigation-menu.md - id: FAS-PFM-CSH-02-04 title: Area access alone does not promise a useful Security menu kind: permission exercises: - CAP-PFM-CSH-006 - CAP-PFM-CSH-007 relies_on: - ATS-PFM-CSH-007-01 preconditions: >- Fixtures cover area-only Security access, access plus one destination key, all keys and no keys. steps: Calculate offered settings areas for each fixture. expected: >- Security is omitted for area-only grants, appears with a readable destination and follows the all-or-none fixtures. negative: true data_needs: >- An isolated browser context and run-owned association fixtures; deterministic authority, response and clock variants where specified. bound_to: - TST-PFM-CSH-022 test_sources: - >- react-console:lib/console/__tests__/settings-area-menu.test.ts#does not offer Security or Maintenance to a person who holds only the areas' access keys - >- react-console:lib/console/__tests__/settings-area-menu.test.ts#offers Security once the person holds one of its links' keys - >- react-console:lib/console/__tests__/settings-area-menu.test.ts#still offers every area to a person who holds everything, and none to a person who holds nothing provenance: test source: >- react-console:lib/console/__tests__/settings-area-menu.test.ts#does not offer Security or Maintenance to a person who holds only the areas' access keys action_evidence: provenance: test source: >- react-console:lib/console/__tests__/settings-area-menu.test.ts#does not offer Security or Maintenance to a person who holds only the areas' access keys assertion_evidence: provenance: test source: >- react-console:lib/console/__tests__/settings-area-menu.test.ts#does not offer Security or Maintenance to a person who holds only the areas' access keys - id: FAS-PFM-CSH-02-05 title: The planned Accounting position survives filtered presentation kind: regression exercises: - CAP-PFM-CSH-006 - CAP-PFM-CSH-008 relies_on: - ATS-PFM-CSH-006-08 - ATS-PFM-CSH-006-09 - ATS-PFM-CSH-006-10 - ATS-PFM-CSH-008-01 preconditions: >- The proposed registry change is compared with the pinned baseline, with custom placements present. steps: >- Compare full and eligible application sequences with CRM and Accounting visible, hidden separately and without custom placements. expected: >- The proposed Accounting adjacency holds whenever both sections survive; other built-in order and placement behavior remain intact. The pinned baseline’s different order remains an implementation finding. negative: false data_needs: >- An isolated browser context and run-owned association fixtures; deterministic authority, response and clock variants where specified. bound_to: [] test_sources: [] provenance: proposed source: >- rhythm-v2-docs:specs/platform/console-shell/planning/features/FEAT-PFM-CSH-02-the-navigation-menu.md action_evidence: provenance: proposed source: >- rhythm-v2-docs:specs/platform/console-shell/planning/features/FEAT-PFM-CSH-02-the-navigation-menu.md assertion_evidence: provenance: proposed source: >- rhythm-v2-docs:specs/platform/console-shell/planning/features/FEAT-PFM-CSH-02-the-navigation-menu.md evidence: - >- rhythm-v2-docs:specs/platform/console-shell/planning/features/FEAT-PFM-CSH-02-the-navigation-menu.md - >- rhythm-v2-docs:specs/platform/console-shell/design/tests/ATS-PFM-CSH-006-find-my-way-through-the-applications-menu.md - >- rhythm-v2-docs:specs/platform/console-shell/design/tests/ATS-PFM-CSH-007-move-into-a-settings-area-and-back-to-my-work.md - >- rhythm-v2-docs:specs/platform/console-shell/design/tests/ATS-PFM-CSH-008-find-the-organizations-own-record-types-in-the-menu.md --- # Finding work through navigation acceptance ## What the Feature Must Do as a Whole This suite follows work through the main menu, settings navigation and customer-defined record placements. Direct entry, menu selection and breadcrumbs are checked together so an administrator can identify the same destination whichever entry path is used. The suite also retains the planned ordering change as an explicit regression obligation. The five scenario kinds are cumulative. Proposed cases remain executable work to assign; bound cases name the exact assertions reviewed and record no passing product run. ## Interactions Between Capabilities Custom placements can make an otherwise unfinished section useful. Settings replace daily navigation and need a return destination, while area offers depend on readable destinations. The recorded Accounting position remains a proposed assertion at these pins; the suite does not present its contrary baseline as passing evidence. ## Regression Record | Revision | Change | Scenarios | Reason | |---|---|---|---| | 1 | initial | all | Establish cumulative acceptance from the pinned capability contracts and existing executable evidence. |