Rhythm 2.0 Specifications

Appearance

ATS-PFM-OPS-016Explain application availability to a customer administrator: Capability Test Specification

Markdown

ATS-PFM-OPS-016

Explain application availability to a customer administrator: Capability Test Specification

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-PFM-OPS-016

Design

Executed by
TST-PFM-OPS-081

KindAcceptance test setProduct areaPlatformModuleOperational RecordsRevision2

Read atservices-platform ad3f6a65react-console baf6dae3macroservice-libraries 54536a44

Explain application availability to a customer administrator: Capability Test Specification ​

Coverage ​

The category map distinguishes authored scenarios from unresolved proof obligations. A bound scenario names an existing executable suite; its recorded result remains unrun.

RuleProof status
BR-CAP-PFM-OPS-016-01ATS-PFM-OPS-016-01, ATS-PFM-OPS-016-06
BR-CAP-PFM-OPS-016-02ATS-PFM-OPS-016-02, ATS-PFM-OPS-016-04
BR-CAP-PFM-OPS-016-03ATS-PFM-OPS-016-03, ATS-PFM-OPS-016-05

Show the same standing with audience-specific detail. The views agree on unavailability while the customer view omits internal decisions and attribution.

Read standing within the administrator’s reach. The local explanation is available without exposing the other customer’s standing.

Keep application availability separate from personal authority. The standing read does not itself grant the person permission to use a protected action.

Evidence and Boundaries ​

Pinned assertion sources support the listed executable bindings. Proposed cases retain the proof required beyond those boundaries. Structured obligations name incomplete object, transition and permission trace; row-level concurrency proof does not establish complete workflow serialization.

Coverage

  • Rule gap: FND-PFM-OPS-068
  • Transition not-applicable
  • Validation gap: FND-PFM-OPS-068
  • Permission covered
  • Edge gap: FND-PFM-OPS-068
  • Failure gap: FND-PFM-OPS-068
  • Boundary covered
  • Concurrency gap: FND-PFM-OPS-068
  • Invariant covered
  • Interaction covered

Test Scenarios

6 scenarios proving CAP-PFM-OPS-016; 3 bound to an existing test.

01 Present the administrator’s application standingpermissionapitest
Proves
BR-CAP-PFM-OPS-016-01
Preconditions
The customer administrator holds the application-read permission.
Steps
Read workspace applications.
Expected
Each application has readable identity, licence dates, operational standing and availability.
Data
Controlled records and caller contexts matching this scenario’s preconditions.
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
02 Protect internal reasons and attributioninvariantapitest
Proves
BR-CAP-PFM-OPS-016-02
Preconditions
Withheld and suspended applications have internal explanations and authors.
Steps
Read through the customer surface.
Expected
Internal commercial and personal details are omitted and withhold is simplified to no licence.
Data
Controlled records and caller contexts matching this scenario’s preconditions.
Bound to
Source
services-platform:modules/licensing/tests/e2e/licensing.e2e.spec.js#says a withheld application is simply not licensed, never that Rhythm withheld it
03 Distinguish foreign workspace from missing authorityboundaryapinegativetest
Proves
BR-CAP-PFM-OPS-016-03
Preconditions
A foreign customer administrator and an unpermitted local user call the read.
Steps
Request the same application listing.
Expected
The foreign workspace is not found and the local caller is refused.
Data
Controlled records and caller contexts matching this scenario’s preconditions.
Bound to
Source
services-platform:modules/licensing/tests/e2e/licensing.e2e.spec.js#answers 404, not 403, to an administrator of another customer holding the same key
04 Show the same standing with audience-specific detailinteractionapiproposed
Proves
BR-CAP-PFM-OPS-013-03 BR-CAP-PFM-OPS-016-02
Preconditions
A reasoned withhold and a suspension are recorded for a workspace.
Steps
Read the staff licensing view and the customer application view.
Expected
The views agree on unavailability while the customer view omits internal decisions and attribution.
Data
Isolated workspace records and caller contexts for both sides of the interaction.
Source
services-platform:modules/licensing/tests/e2e/licensing.e2e.spec.js#tells staff the same application was withheld, which is the distinction the two answers keep; services-platform:modules/licensing/tests/e2e/licensing.e2e.spec.js#says a withheld application is simply not licensed, never that Rhythm withheld it; CAP-PFM-OPS-013;
05 Read standing within the administrator’s reachinteractionapiproposed
Proves
BR-CAP-PFM-OPS-016-03
Preconditions
Two customers have workspaces with different application standing.
Steps
Read the local workspace and then request the other customer’s application information.
Expected
The local explanation is available without exposing the other customer’s standing.
Data
Isolated workspace records and caller contexts for both sides of the interaction.
Source
services-platform:modules/licensing/tests/e2e/licensing.e2e.spec.js#answers 404, not 403, to an administrator of another customer holding the same key; CAP-PFM-SEC-002;
06 Keep application availability separate from personal authorityinteractionapiproposed
Proves
BR-CAP-PFM-OPS-016-01
Preconditions
A licensed ready application is available to the workspace but the person lacks its application authority.
Steps
Read workspace standing and request a protected action as that person.
Expected
The standing read does not itself grant the person permission to use a protected action.
Data
Isolated workspace records and caller contexts for both sides of the interaction.
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; CAP-PFM-SEC-007;

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