Rhythm 2.0 Specifications

Appearance

FAS-PFM-CSH-04Application access in the console acceptance

Markdown

FAS-PFM-CSH-04

Application access in the console acceptance

Markdown
  • DocumentProposed
  • Product intentProposed

Planning

Feature
FEAT-PFM-CSH-04
Capabilities
CAP-PFM-CSH-014, CAP-PFM-CSH-015, CAP-PFM-CSH-016, CAP-PFM-CSH-017
Executed by
TST-PFM-CSH-011, TST-PFM-CSH-035

Product areaPlatformModuleConsole Shell and NavigationRevision1

Read atrhythm-v2-docs 25e253cbreact-console baf6dae3services-platform ad3f6a65

Application access in the console acceptance ​

What the Feature Must Do as a Whole ​

This suite connects context-derived application authority, destination refusal, refreshed menu choices and the administrator’s overview. It examines a change during an existing session as well as fresh entry. The cases distinguish organization availability from a person’s task authority so the launcher and explanations can be judged together.

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 ​

A coded service refusal can update offered applications while retaining the other access snapshots. Product absence takes precedence over task denial, and the overview has its own guard. Customer response redaction is an API assertion; it does not prove every browser explanation or a full refresh of withdrawn roles.

Regression Record ​

RevisionChangeScenariosReason
1initialallEstablish cumulative acceptance from the pinned capability contracts and existing executable evidence.

Scenarios

5 scenarios proving FEAT-PFM-CSH-04 as a whole.

01 An unavailable destination leads to an understandable overview behaviour proposed
Exercises
CAP-PFM-CSH-014 CAP-PFM-CSH-015 CAP-PFM-CSH-017
Relies on
ATS-PFM-CSH-015-04 ATS-PFM-CSH-015-07 ATS-PFM-CSH-017-03
Preconditions
An association administrator can view Applications while Membership is unavailable.
Steps
Open Members directly, follow View Applications and inspect the Membership row.
Expected
The blocked page explains application unavailability; the overview identifies the organization’s state without presenting the destination as authorized.
Data
An isolated browser context and run-owned association fixtures; deterministic authority, response and clock variants where specified.
Source
rhythm-v2-docs:specs/platform/console-shell/planning/features/FEAT-PFM-CSH-04-applications-in-the-console.md
02 A coded refusal corrects the existing launcher interaction test
Exercises
CAP-PFM-CSH-014 CAP-PFM-CSH-016
Relies on
ATS-PFM-CSH-016-01 ATS-PFM-CSH-014-06
Preconditions
CRM and Membership are offered; CRM is then withdrawn in the mock authority response.
Steps
Trigger the application refusal by navigating to Tasks without reloading the browser.
Expected
CRM leaves the sidebar and Membership remains after the application refresh.
Data
An isolated browser context and run-owned association fixtures; deterministic authority, response and clock variants where specified.
Bound to
Source
react-console:e2e/mock/application-access.mock.spec.ts#brings the launcher up to date instead of leaving it offering what is gone
03 A returning tab replaces applications without replacing other authority lifecycle proposed
Exercises
CAP-PFM-CSH-014 CAP-PFM-CSH-016
Relies on
ATS-PFM-CSH-016-03 ATS-PFM-CSH-016-05 ATS-PFM-CSH-016-08
Preconditions
The tab has an aged list and a subsequent context answer changes applications, features, rules and roles.
Steps
Return the visible tab at the refresh threshold and inspect the installed context and menu.
Expected
Applications and features change; the previous roles, rules and reachable workspaces remain, with the documented full-context refresh disagreement still open.
Data
An isolated browser context and run-owned association fixtures; deterministic authority, response and clock variants where specified.
Source
rhythm-v2-docs:specs/platform/console-shell/planning/features/FEAT-PFM-CSH-04-applications-in-the-console.md
04 Product availability and task grants remain separate permissionnegative proposed
Exercises
CAP-PFM-CSH-014 CAP-PFM-CSH-015 CAP-PFM-CSH-017
Relies on
ATS-PFM-CSH-014-05 ATS-PFM-CSH-015-01 ATS-PFM-CSH-015-02 ATS-PFM-CSH-017-12
Preconditions
Fixtures vary enabled CRM, contact-view authority and overview-view authority independently.
Steps
Visit the contact destination and Applications overview in each fixture.
Expected
Application absence wins over task denial; an enabled but unauthorized task is refused, and the overview requires its own view authority.
Data
An isolated browser context and run-owned association fixtures; deterministic authority, response and clock variants where specified.
Source
rhythm-v2-docs:specs/platform/console-shell/planning/features/FEAT-PFM-CSH-04-applications-in-the-console.md
05 Customer application facts exclude staff commercial detail regression test
Exercises
CAP-PFM-CSH-017
Relies on
ATS-PFM-CSH-017-11
Preconditions
A permitted customer administrator reads fixtures with grant, withholding and suspension.
Steps
Read the administrator application API after each fixture is established.
Expected
The answer retains readable application facts while excluding overrides, staff identities and staff-authored commercial reasons; withholding is reported as unlicensed.
Data
An isolated browser context and run-owned association fixtures; deterministic authority, response and clock variants where specified.
Bound to
Source
services-platform:modules/licensing/tests/e2e/licensing.e2e.spec.js#answers each application with its key, name, licence state and dates, operation state and availability

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software