Get started with tenant-aware simpleXflow projects.
Use simpleXflow to model simulation-oriented process systems in the browser, save them per tenant, and present reproducible paper examples.
Create or open a project
Open an existing tenant project from the left workspace list, or use the plus button to start a clean draft.
Use the editor palette to add events, tasks, gateways, resources, queues, buffers and annotations.
Name the project, check the visual model, then save it into the current tenant workspace.
simpleXflow project files
Projects are stored as tenant-scoped records. The visual model is carried as BPMN-compatible XML so older visualizer exports can still be opened while the WebApp presents them as simpleXflow projects.
Isolated team workspaces
Every signed-in user belongs to a tenant. Project lists, imported files and saved drafts are filtered by that tenant, so presentation and team data stay separated.
Use existing files
Import `.bpmn`, `.xml` or `.zip` files from the previous visualizer. ZIP files are scanned for the first project model and saved as a new simpleXflow project.
Architecture and logic
The migrated editor keeps the architecture, split and logic views from the original tool, including the properties panel and the simpleXflow-specific palette behavior.
Paper and poster samples
Use this to explain architecture-level routing, resource assumptions and the bridge from system architecture to local logic.
Use this compact sample to connect simpleXflow notation with classical discrete-event simulation structures.
Use this for the emergency-room scenario with admission, room assignment, treatment logic, ward routing and disinfection.
When nothing reacts
Refresh the page once after a deployment. The Projects page runs as an interactive Blazor Server screen; after the connection is active, plus, import, load and save respond immediately.
What gets persisted
Save reads XML from the visual editor. If the editor cannot return XML, simpleXflow saves the last known model and shows a warning instead of losing the draft.
Build first, deploy manually
Commits build and publish the container image. Production deployment is triggered manually from the GitHub Actions deploy workflow.
Recommended flow
Load a sample, explain the visual model, adapt one element, then save it. This proves import, modeling, tenant storage and presentation readiness in one short sequence.