Description

Starting with version 2.16, a new workflow simulator has been introduced to support workflow development and testing.

To edit a workflow, navigate to Orchestration → Editor and click the pencil icon next to the desired workflow.

The edit page now includes two additional tabs: Simulate and Validate.

Simulate Tab

On this page, you can simulate workflow execution by providing the input data that would typically be received by the Core, including:

• http method
• content type
• url
• url template (for matching url segments)
• body
• username (of the original requester)

Clicking the Simulate button initiates the simulation. Execution paths are highlighted in green, and nodes that have been traversed are marked with a green checkmark.

If an error occurs during the simulation, the affected node will be marked with a red indicator.

At the bottom of the page, a Timeline panel displays all context variables along with their updated values at each step of the execution.

Adding mock data

For nodes that interact with external systems, simulations can be performed without making actual external calls by supplying mock responses instead.

Mocking is supported for the following node types:

• all http call nodes
• trigger manual action node
• require user approval node
• wait callback node

Example mock data control for http nodes:

INFO

Mock data controls are only available within the Simulate tab.

During simulation, mock data will be used only if the Use mock data checkbox is selected. Once the simulation is complete, you can click the Save button to store the simulation inputs, results, and any mock data used.

Validate Tab

This tab displays all previously saved simulations.

Clicking the Load button will populate the Simulate tab with the saved input and mock data, allowing you to manually re-run the simulation.

The Replay button executes the simulation again and checks whether the output matches the previously saved result.

By default, simulations are replayed without using mocks, but you can choose to include them if needed.

If the outputs match, a confirmation modal will appear:

If differences are detected, a modal highlighting the mismatches will be shown:

Saved simulations can be deleted by clicking the red X button.