Skip to content

Release v4.44.0

Choose a tag to compare

@github-actions github-actions released this 16 Oct 04:36
5d915a2

The CRM domain blueprint of Part B 3.1 of the screen blueprints specification: a ready-to-use sales application on top of the foundation set, with its navigation and two sample-data packs.

Added

  • @cratis/scene.blueprint.crm, a blueprint package (domain crm, category Business / CRM) that depends on the foundation set only through its public templates and components: eighteen screen templates, five dialog templates and eighteen ready-to-use screens.
    • CrmDashboard: open pipeline value, won this month and conversion rate; leads by source and deals by stage as a funnel; deals closing soon; my tasks.
    • CrmLeadList, CrmContactList, CrmCompanyList, CrmActivityList: name, company, owner, status and last contact; filters by owner, status, source and created date; row actions edit, assign, convert (leads) and delete; choosing a contact or company opens its page.
    • CrmDealPipeline (a column for each stage with the stage's value in its header, a card for each deal) and CrmDealList (the same deals grouped by stage with subtotals).
    • CrmContactPage, CrmCompanyPage, CrmDealPage: key facts, tabs, the record, related lists, activity and next steps.
    • Crm<Entity>CreateForm and Crm<Entity>EditForm for leads, contacts, companies and deals, and CrmQuickCreate<Entity> dialogs for those and activities.
    • Each template carries its scopes, so a template picker offers it only where it fits and hides the blueprint where nothing applies.
  • Navigation of the application: a topbar naming the crm module and the module's sidebar (Dashboard, Leads, Contacts, Companies, Deals with Pipeline and List, Activities), the application structure, and crmApplication() that assembles the document.
  • Sample-data packs crm-enterprise-en (en-GB, GBP) and crm-nordic-smb (nb-NO, NOK) answering the same shapes; the pack's one-row CrmSettings shape gives every figure and date its locale and currency.
  • Specifications for the definition of done per template and package, the screen set agreeing with the manifest, structure and navigation, applicability by level, every screen previewed in both packs with no accessibility violation, every standard state forced on the main screens, the behaviors of the application (open a quick-create dialog, choose a row, edit, move a deal between stages), and a Chromium audit of every screen and dialog at desktop, tablet and phone widths in the light and dark themes.
  • Docs: blueprints/crm-blueprint.md.

Part of #110