Add flow purpose categories and deployment demo
This commit is contained in:
@@ -14,6 +14,7 @@ The initial landscape contains Website, API, ERP, CRM and Email Platform plus tw
|
||||
- **Place order:** Website → API → ERP, followed by parallel CRM and Email Platform updates.
|
||||
- **Register customer:** Website → API → CRM → Email Platform.
|
||||
- **Monday demo journeys:** Contact enquiry, Sample request, Commercial order, and Order retry and recovery.
|
||||
- **Deployment demo:** Build Server → Octopus release → Sitecore CM and two CD targets, with parallel target outcomes.
|
||||
|
||||
## Features
|
||||
|
||||
@@ -26,6 +27,9 @@ The initial landscape contains Website, API, ERP, CRM and Email Platform plus tw
|
||||
- Model physical operations alongside software with Physical Location and Business Operation categories, plus Physical Goods and Human Task relationships. The Warehouse preset includes receiving, storage, picking, dispatch and returns with clearly labelled physical-goods ports and fictional shipment payloads.
|
||||
- Run the mixed Physical goods receipt demo: SAP purchase order → Supplier shipment → Warehouse → Warehouse Operative decision → Warehouse Management System → SAP confirmation. Physical locations remain independent from their software systems; all transfers are simulated and inspectable.
|
||||
- Model persistent database integrations separately from activity: Direct Database Access, Scheduled Import, Replication / Sync and File Transfer. Configure access mode, trigger/frequency, source tables/views/queries, destination, authoritative source and an optional simulated mapping. Live query requests and returned database rows are separate connections; scheduled imports identify downstream copies such as Sitecore items.
|
||||
- Separate flow purpose from cable relationship, payload type and integration mechanism. Scenarios have editable purposes for Business Transactions, Content & Reference Data, Build & Deployment, Operations & Monitoring, Identity & Access and Physical Logistics; individual transfers can override the scenario purpose and connections can carry multiple purposes without duplicating cables.
|
||||
- Filter flow purposes independently from system categories, colour active packets by purpose and use the accessible purpose legend. Deployment cables retain their relationship styling while the packet colour communicates Build & Deployment.
|
||||
- The deployment demo carries fictional package, release, version, environment and target fields through a sequential package/release step and a parallel CM/CD target step. Each target has an independent simulated outcome; no build or deployment system is contacted.
|
||||
- Compare the example Sitecore live-query and scheduled-import scenarios for the fictional Product / Literature / Webinar Management application and MSSQL database. Database payloads are sample rows/JSON only; no database connection or inventory/accounting engine is implemented.
|
||||
- Place reusable Website, CRM, ERP, Email Platform, Analytics and API presets, selecting only the capabilities needed for each instance.
|
||||
- Browse the layered preset library from the Presets tab: searchable system/product catalog entries, shared capabilities, deployment layouts and starter kits. Entries include tags, version metadata and official documentation sources; favourites are stored locally.
|
||||
@@ -46,4 +50,4 @@ npm run build
|
||||
|
||||
## Limitations
|
||||
|
||||
This is intentionally a local simulation prototype. It has no authentication, collaboration, server persistence, external API calls, real payload delivery, or production-grade graph editing. Custom definitions and placed instances are stored in browser local storage; playback state is transient and is not included in saved JSON. LiteGraph supplies canvas rendering and cable interaction; scenario semantics are managed by the Vue application. The minimap is diagnostic rather than a full viewport navigator, and transformation highlighting currently compares top-level JSON fields. Pipeline mappings are deliberately limited to the listed rule operations; arbitrary JavaScript, network lookups and live middleware execution are not supported. The custom builder exposes pipeline definitions as validated JSON so advanced step graphs can be edited without adding another runtime dependency. Preset documentation URLs are reference metadata only; the simulator does not inspect or synchronize vendor products.
|
||||
This is intentionally a local simulation prototype. It has no authentication, collaboration, server persistence, external API calls, real payload delivery, or production-grade graph editing. Custom definitions and placed instances are stored in browser local storage; playback state is transient and is not included in saved JSON. LiteGraph supplies canvas rendering and cable interaction; scenario semantics are managed by the Vue application. The minimap is diagnostic rather than a full viewport navigator, and transformation highlighting currently compares top-level JSON fields. Pipeline mappings are deliberately limited to the listed rule operations; arbitrary JavaScript, network lookups and live middleware execution are not supported. The custom builder exposes pipeline definitions as validated JSON so advanced step graphs can be edited without adding another runtime dependency. Flow categories are simulation metadata and do not enforce model behaviour; a packet can be displayed on one selected category at a time even when a connection supports multiple categories. Preset documentation URLs are reference metadata only; the simulator does not inspect or synchronize vendor products.
|
||||
|
||||
Reference in New Issue
Block a user