Rhythm 2.0 Specifications

Appearance

ATS-PFM-OPS-013Explain workspace licensing to Rhythm staff: Capability Test Specification

Markdown

ATS-PFM-OPS-013

Explain workspace licensing to Rhythm staff: Capability Test Specification

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-PFM-OPS-013

Design

Executed by
TST-PFM-OPS-053, TST-PFM-OPS-081

KindAcceptance test setProduct areaPlatformModuleOperational RecordsRevision2

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

Explain workspace licensing to Rhythm staff: 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-013-01ATS-PFM-OPS-013-01, ATS-PFM-OPS-013-08, ATS-PFM-OPS-013-09
BR-CAP-PFM-OPS-013-02ATS-PFM-OPS-013-02, ATS-PFM-OPS-013-07
BR-CAP-PFM-OPS-013-03ATS-PFM-OPS-013-03
BR-CAP-PFM-OPS-013-04ATS-PFM-OPS-013-04
BR-CAP-PFM-OPS-013-05ATS-PFM-OPS-013-05
BR-CAP-PFM-OPS-013-07ATS-PFM-OPS-013-06

Review a withdrawn exception in staff history. The same decision remains explainable with its original reason and revocation attribution.

Expose synchronization health alongside retained commercial evidence. Staff can distinguish retained commercial evidence from an unsuccessful refresh.

Refresh the licensing explanation after suspension. The read presents the changed readiness alongside the retained commercial coverage.

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 covered
  • Transition not-applicable
  • Validation covered
  • Permission covered
  • Edge gap: FND-PFM-OPS-065
  • Failure gap: FND-PFM-OPS-016
  • Boundary gap: FND-PFM-OPS-065
  • Concurrency gap: FND-PFM-OPS-065
  • Invariant gap: FND-PFM-OPS-065
  • Interaction covered

Test Scenarios

9 scenarios proving CAP-PFM-OPS-013; 4 bound to an existing test.

01 Expose licensing context only to authorized staffpermissionapitest
Proves
BR-CAP-PFM-OPS-013-01
Preconditions
A workspace has present and past decisions.
Steps
Read licensing as HQ staff and a customer caller.
Expected
Only staff receive the complete application and decision context.
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 the overrides behind the decision, with the reason and the author of each
02 Retain a withdrawn decisionruleapitest
Proves
BR-CAP-PFM-OPS-013-02
Preconditions
An override has been revoked.
Steps
Read staff licensing detail.
Expected
The decision remains with its revocation information.
Data
Controlled records and caller contexts matching this scenario’s preconditions.
Bound to
Source
services-platform:modules/licensing/tests/e2e/licensing.e2e.spec.js#keeps a revoked override in the answer, because the trail is what the screen is for
03 Keep the staff-only withhold distinctionruleapitest
Proves
BR-CAP-PFM-OPS-013-03
Preconditions
An effective override withholds an application.
Steps
Read staff and customer licensing detail.
Expected
Only staff receive the explicit withhold explanation.
Data
Controlled records and caller contexts matching this scenario’s preconditions.
Bound to
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
04 Present names and gate panel actionspermissionbrowserproposed
Proves
BR-CAP-PFM-OPS-013-04
Preconditions
Reader and manager accounts inspect past and current decisions.
Steps
Open the panel with each account.
Expected
Both see readable names and folded history while only management authority receives actions.
Data
Controlled records and caller contexts matching this scenario’s preconditions.
Source
react-console:e2e/dev/hq-licensing.dev.spec.ts#the panel lists the Fictional Association's applications, names every author and folds the past overrides away
05 Validate the dialog’s explanation and periodvalidationbrowsernegativetest
Proves
BR-CAP-PFM-OPS-013-05
Preconditions
A customer-workspace grant dialog is open.
Steps
Supply an insufficient reason and then omit the end date.
Expected
Submission remains blocked until both requirements are met.
Data
Controlled records and caller contexts matching this scenario’s preconditions.
Bound to
Source
react-console:e2e/mock/application-access.mock.spec.ts#asks for a reason long enough to be one
06 Restore the failed-setup retry integrationfailurebrowserproposed
Proves
BR-CAP-PFM-OPS-013-07
Preconditions
An application has failed preparation.
Steps
Use Retry Provisioning from its panel.
Expected
The corrected integration invokes setup and refreshes the resulting state.
Data
Controlled records and caller contexts matching this scenario’s preconditions.
Source
react-console:lib/hq/licensing.ts:licensingPaths.application ("retry-provisioning"); services-platform:modules/licensing/aws/api/licensing.routes.ts:retryTenantApplicationProvisioning ("retry_provisioning")
07 Review a withdrawn exception in staff historyinteractionapiproposed
Proves
BR-CAP-PFM-OPS-011-04 BR-CAP-PFM-OPS-013-02
Preconditions
Staff have written a reasoned application exception.
Steps
Withdraw it and reopen the licensing panel’s historical decisions.
Expected
The same decision remains explainable with its original reason and revocation 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#refuses to withdraw the same override twice, with 409; services-platform:modules/licensing/tests/e2e/licensing.e2e.spec.js#keeps a revoked override in the answer, because the trail is what the screen is for; CAP-PFM-OPS-011; WF-PFM-OPS-010; WF-PFM-OPS-012
08 Expose synchronization health alongside retained commercial evidenceinteractionapiproposed
Proves
BR-CAP-PFM-OPS-012-08 BR-CAP-PFM-OPS-013-01
Preconditions
Staff can read a company with a previously successful synchronization.
Steps
Cause a provider failure, then inspect company contracts, health and workspace licensing.
Expected
Staff can distinguish retained commercial evidence from an unsuccessful refresh.
Data
Isolated workspace records and caller contexts for both sides of the interaction.
Source
services-platform:modules/licensing/tests/integration/services/sync/sync-company-licences.integration.spec.js#changes no snapshot, no window and no last success; services-platform:modules/licensing/tests/e2e/licensing.e2e.spec.js#answers the overrides behind the decision, with the reason and the author of each; CAP-PFM-OPS-012; WF-PFM-OPS-010; WF-PFM-OPS-012
09 Refresh the licensing explanation after suspensioninteractionapiproposed
Proves
BR-CAP-PFM-OPS-013-01 BR-CAP-PFM-OPS-015-02
Preconditions
Staff can manage an enabled licensed application.
Steps
Suspend it with a reason and reread staff licensing.
Expected
The read presents the changed readiness alongside the retained commercial coverage.
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 the overrides behind the decision, with the reason and the author of each; services-platform:modules/licensing/tests/integration/services/enablement/provision-tenant-application.integration.spec.js#refuses every move for an application the tenant has never been provisioned for; CAP-PFM-OPS-015; WF-PFM-OPS-010; WF-PFM-OPS-012

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