Skip to main content

Process

Create, version, and deploy the workflows that power your automation — all from a single page.

A Process is a workflow project in EW-FLOW. It contains your BPMN diagram, its version history, and links to the Environments where it runs. Every workflow you build starts here.

Process list page showing all Processes in the current Workspace

How it works​

Each Process goes through a lifecycle: you create it, design the workflow in the BPMN editor, save versions as you iterate, and deploy a version to an Environment so the engine can execute it. Processes are scoped to the current Workspace and can be linked to one or more Environments.

Fields​

  • Id — unique identifier of the Process. Useful when contacting support.
  • Process Name — the name you gave the Process during creation. This field is editable.
  • Summary — a description of your Process. This field is editable.
  • Last Update — date and time of the last Save or Deploy action.
  • Actions — menu to perform operations on the Process.

Actions​

Edit​

Update the Process Name or Summary.

  1. Click the Actions menu on the Process row.
  2. Select Edit.
  3. Modify the fields you need.
  4. Click the Actions menu again and select Save to confirm, or Cancel to discard.

Delete​

Permanently remove a Process from the Workspace. A confirmation dialog appears before deletion.

info

A deleted Process can only be recovered by contacting customer support.

Process History​

View all saved versions of the Process, including who created each version and when.

  1. Click Actions → Process History.
  2. Browse the version list.
  3. Click the dotted menu on any version to open it in the editor.
warning

If you deploy or save an older version, it becomes the active version the engine uses for execution.

Sessions​

Opens the Sessions page filtered to this Process.

Environment​

Displays the Environments linked to this Process — including creation date, last update, and a link to open the latest saved version in each Environment.

Creating a Process​

  1. Navigate to Process from the sidebar.
  2. Click Add Process in the top-right corner.
  3. Enter a name and an optional description.
  4. Choose a template to jumpstart your workflow (or select Empty for a blank slate).
  5. Create or select an Environment for the Process.

Template selection showing available starter workflows

Templates​

  • Medical Appointment Booking — a multi-path workflow that handles booking, modifying, and cancelling appointments. Collects service type, healthcare system, doctor preference, and personal data.
  • Empty — a complete blank slate with no pre-built nodes.
  • Hello World — a minimal workflow with one input and one output.

After creation, a dialog asks whether you want to configure the Environment now or go straight to the BPMN editor.

warning

In the current version you cannot add a new Environment to a Process after creation, so plan accordingly.

Process Editor​

The Process Editor is where you design your workflow visually. Drag BPMN elements onto the canvas, connect them with Sequence Flows, and configure each node's data.

Process editor canvas with a sample workflow

Without any Modules installed, the editor behaves like a standard BPMN editor. Installing Modules from the Marketplace adds Task types that give your workflow real functionality.

To learn more, see BPMN Editor.

Deployments​

The Deployments page is available from the sidebar and shows all Deployment records for your Workspace.

Deployments page showing deployment status, environment, and timestamps

  • Status — whether the Deployment succeeded or failed.
  • Environment — the target Environment.
  • Process — the Process that was deployed.
  • Created At — when the Deployment was triggered.

Click the expand arrow on any row to view that Deployment's logs.

Chat​

The Chat button in the editor toolbar opens a test chat panel on the right side. Use it to interact with the latest deployed version of your Process in real time. Sessions created from test chats appear on the Sessions page.

Best practices​

  1. Save frequently — each save creates a version you can roll back to if needed.
  2. Use descriptive summaries — a clear summary helps collaborators understand what the Process does without opening the editor.
  3. Test before deploying to production — use the Chat panel or a dedicated test Environment to verify behavior.
  • BPMN Editor — learn how to use the visual editor.
  • Environments — configure the runtime settings for your Process.
  • Sessions — inspect execution data from your deployed workflows.