Versions and stages

Every time you save a workflow in Pulse, a new version is created. This gives you a full history of every change made to the workflow — and the ability to review or restore a previous state at any time. A workflow’s stage, areas and, for On Field Update workflows, trigger fields are not part of a version. You choose them when you create the workflow, and areas and trigger fields can be changed at any time without creating a new version.

Saving a workflow

Click the Save button in the top toolbar to save your changes. A dialog appears with the following fields:

Name — the name shown in the Pulse dashboard. Required.
Note — an optional description of what changed in this version. Useful for keeping a clear changelog.

Each save creates a discrete version with its own timestamp and the name of the user who saved it.

You cannot activate a workflow with unsaved changes. Save your work before toggling the workflow to active.

Stages

A workflow’s stage is the point in request processing where it runs. You pick it when you create the workflow, and it can’t be changed afterwards. To run the same logic at another point, create a new workflow for that stage.

Stage	When the workflow runs
Can Classify	When a request arrives, before any processing. Decide whether to process, delay, or ignore it.
On Classification	Right after the request’s intent is classified.
Can Extract	After classification, before extraction. Like Can Classify, but the intent is known.
On Extraction	Right after data is extracted, before internal transformations.
On Account Resolution	After extraction, to resolve the customer account.
On Transformation	After internal transformations. The main point for business logic and ERP validation.
On Confirmation	When a request is confirmed, manually or autonomously.
On Field Update	When a user changes one of the workflow’s trigger fields in Flow. See On Field Update.
None	Never — request processing does not call it. Useful for drafts and experiments.

The stage is shown in the Stage column on the Pulse dashboard and as a badge next to the workflow name in the editor. Some nodes are only available in certain stages — for example, an Intent Switch needs a stage where the intent is known. For the data each stage receives and can return, see the integration data contract. For which stage fits which job, see Stages and what each one returns.

Areas

A workflow’s areas decide which requests it runs for. A workflow with specific areas only runs for requests in those areas. Default means the workflow runs for requests in all areas. You choose areas right after picking the stage when you create a workflow, and you can change them later in two places:

In the editor — click the areas chip next to the workflow name in the top toolbar.
On the Pulse dashboard — click a workflow’s Areas cell.

Select or clear areas, then click Save in the picker. Clicking Cancel or outside the picker discards your changes.

Changing areas on a saved workflow applies immediately and does not create a new version. If the workflow is Active, it starts or stops running for those areas right away.

If your user group is restricted to specific areas, Default isn’t available and you need to select at least one area. Areas outside your access are shown but can’t be selected. See Areas for how areas are set up.

On Field Update

An On Field Update workflow runs the moment a user saves a change to one of its trigger fields in Flow, for example a line’s quantity or a header discount. The values it writes are saved with the user’s change, so the reviewer sees the recalculated request straight away. Use Calculate nodes for the arithmetic.

Trigger fields

When you create an On Field Update workflow, a third step follows the areas: Choose trigger fields. Pick the fields whose change should run the workflow, grouped by header, product line, sub product and address. Select at least one field. The summary at the bottom, such as “When Quantity changes”, is also shown under the webhook node on the canvas.

To change them later, click the trigger fields chip (the one with the lightning icon) next to the areas chip in the top toolbar, select or clear fields, and click Save.

Trigger fields picker — Changing the trigger fields from the toolbar

Like areas, changing the trigger fields of a saved workflow applies immediately and does not create a new version. Don’t pick a field the workflow itself writes: the values a workflow writes don’t run it again.

What happens when a user edits a field

The user changes a field in Flow, for example the quantity on line 1 from 4 to 6.
If an active On Field Update workflow for the request’s area has that field as a trigger, it runs right away, with the full request and the list of changed fields.
The fields the workflow writes are saved, as if the user had changed them too. Changed values are highlighted in Flow.
If any of the changed fields has Simulate on update switched on, the request is then simulated as usual, with the new values.

Flow before the change — Before: line 1 has quantity 4 and total price 50

Flow after the change — After changing the quantity to 6: both lines get the 10% header discount, and the order total adds up the lines plus freight

Order total in the summary — The order total in the summary, written by the second Calculate node

Which calculation wins

Go Autonomous has some built-in calculations, such as a line’s total price from its unit price and quantity. A field update hook replaces them for its trigger fields:

When a field is a trigger of an On Field Update workflow, the workflow runs instead of the built-in calculation for that field. If the workflow fails, times out or the request is busy, the built-in calculation runs instead, so the field is never left stale. An empty answer counts as an answer.
A workflow wins over a third-party connector’s On Field Update hook for the same field. The connector still runs for fields no workflow is watching.
Fields with no workflow and no connector hook keep the built-in behaviour.

This is decided per field and per area: a workflow published for one area doesn’t change anything for requests in other areas.

On Field Update workflows run while the user waits, so keep them small and fast. Calculate nodes run in milliseconds. An HTTP node that calls a slow system makes every edit feel slow.

On Field Update workflows can’t be tested from a stored request with an Input node, because they need a concrete field change. Paste a sample payload into an Input node instead, or check the executions after editing a field in Flow.

Version history

To view all previous versions of a workflow, click the version history button in the top toolbar. A drawer opens on the right side of the editor showing every saved version, each with:

The version timestamp
Who saved it
The note added at the time of saving (if any)

You can review the configuration of any previous version from this drawer. This is useful for understanding what changed between versions or rolling back to an earlier state if needed.

Activating and deactivating

Use the Active toggle in the top toolbar to turn a workflow on or off.

Active — the workflow is live and will process matching incoming requests automatically.
Inactive — the workflow is saved but will not process any requests.

Toggling a workflow active requires the current version to be saved. If there are unsaved changes, you will be prompted to save first. You can also toggle workflows active or inactive directly from the Pulse dashboard without opening the editor.

Getting Started

Workstation

Flow

Axon

Pulse

Decision Analytics

Saving a workflow

Stages

Areas