Skip to content

Release v4.53.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 16 Oct 06:48
v4.53.0
90a5821
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

The Approvals and Requests domain blueprint of Part B 3.3 of the screen blueprints specification, shaped like the CRM and Ticketing blueprints.

Added

  • @cratis/scene.blueprint.approvals, a blueprint package (domain approvals, category Business / Approvals): seven screen templates, two dialog templates and seven ready-to-use screens.
    • ApprovalInbox: the requests waiting for the signed-in person as cards (the foundation list's Cards variant) with Approve, Reject and Request changes as buttons on each card; a decision opens DecisionDialog.
    • MyRequests (draft, submitted, approved, rejected as chips, and a New request button), AllRequests and RequestTypes (the request types an organisation offers, for administrators).
    • NewRequestWizard: request type, details, attachments (a file uploader), then review and submit, on the foundation WizardScreen.
    • RequestPage: summary, the approval chain (approvalChainStepper), the request's fields, attachments and the comments as the page's activity, and the decision buttons.
    • RequestTypeEditForm, and dialogs DecisionDialog (a confirmation with the decision and a comment) and RequestTypeQuickCreate.
    • Each template carries its scopes, so a template picker offers it only where it fits.
  • Navigation: a topbar naming the approvals module and the module's sidebar (Inbox, My requests, All requests, Templates), the application structure and approvalsApplication().
  • Sample-data packs approvals-general (en-GB, GBP) and approvals-nordic (nb-NO, NOK) answering the same shapes, with five request types as presets (Leave, Expense, Purchase, Travel, Invoice approval).
  • Specifications: definition of done per template and package, screen set consistency, applicability by level, every screen previewed in both packs with no accessibility violation, standard states forced on seven screens, the behaviors of the application (decide from the inbox, start and step through the wizard, open a request and its chain, edit a request type), and a Chromium audit of every screen and dialog at desktop, tablet and phone widths in light and dark themes (56 specs, in CI).
  • Docs: blueprints/approvals-blueprint.md.

Part of #112

Assets 2
Loading