diff --git a/README.md b/README.md index 1c567b1..70f48b5 100644 --- a/README.md +++ b/README.md @@ -15,6 +15,7 @@ The initial landscape contains Website, API, ERP, CRM and Email Platform plus tw - **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. +- **Process analysis demo:** Sitecore → Sample Request Application → manual CRM entry → SAP → Customer Service → Lab / Warehouse → Sample Shipment, with customer and sales notification branches. ## Features @@ -38,6 +39,8 @@ The initial landscape contains Website, API, ERP, CRM and Email Platform plus tw - Add restricted transformation pipelines to action definitions for middleware-style Receive, Validate, Transform, Route and Send stages. Pipelines support explicit example payloads, copy/rename/fixed/default/type-conversion/object-construction/array-item-mapping rules, reference lookup values, validation-failure paths and playback inspection without executing arbitrary JavaScript. The demo includes Website → Order Middleware → ERP. - Model direct request/response exchanges separately from onward event transfers. Request and response payloads are both recorded in the data inspector, with compatibility warnings shown without blocking unusual integrations. - Run, pause, advance and reset scenarios with animated packets and event log output. +- Analyse an end-to-end process over an existing scenario with a start event, intended/alternative/rejection/cancellation outcomes, required milestones, owner and operation metadata, queue/trigger information, modelled processing/waiting estimates, evidence status, correlation IDs and local record mappings. +- Compare Current State and Proposed State process versions without overwriting the existing process. The analysis highlights the intended path, keeps notification/side-effect branches separate, and reports missing onward paths, unowned handoffs, manual re-entry, untracked notifications and unknown transitions as review findings. - Adjust playback speed and inspect the active payload. - Persist the complete landscape, including node positions, in browser local storage. - Export and import the landscape as JSON. Invalid imports and deleted connection references are rejected with actionable errors. @@ -50,4 +53,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. 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. +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. Process findings are review prompts based on configured model data, not proof of operational failure; processing and waiting durations are modelled estimates unless explicitly supported by measured evidence. Preset documentation URLs are reference metadata only; the simulator does not inspect or synchronize vendor products. diff --git a/src/App.vue b/src/App.vue index 9413a4d..8161e44 100644 --- a/src/App.vue +++ b/src/App.vue @@ -1,7 +1,7 @@