Run and Debug Diagrams

Ed can run BPMN diagrams while you author them. Use this to validate process flow, script behavior, form rendering, and task data before moving a model into Spiff Arena.

Run While Building

Run the diagram after meaningful changes such as:

  • adding or rewiring sequence flows;

  • changing a gateway condition;

  • editing a Script Task;

  • adding a User Task form;

  • changing a service task configuration;

  • adding a subprocess or call activity.

When the process reaches a User Task, provide sample data that matches the rendered form schema. Continue the run until it completes, reaches an expected wait state, or exposes an error that needs to be fixed.

What to Inspect

During a run, inspect:

  • current task status;

  • task data values;

  • form schema and UI schema rendering;

  • script output variables;

  • branch choices after gateways;

  • service task errors or connector proxy configuration problems.

Debugging Form Problems

For User Task forms, check these items first:

  • The JSON Schema and UI Schema filenames match the intended form.

  • The rendered schema is valid JSON after Jinja rendering.

  • The UI Schema references fields that exist in the JSON Schema.

  • Required hidden fields have defaults or are set before the form renders.

  • Date and numeric validations match the actual submitted value type.

Debugging Flow Problems

For process flow problems, check:

  • Every task in the active path has incoming and outgoing sequence flows.

  • Exclusive gateway conditions evaluate to booleans.

  • A gateway with a fallback has an explicit default flow.

  • Loop paths return to the intended gateway or task.

  • Call activities point to the correct process and file.

If the issue only appears after deployment, compare the Ed workspace files with the files deployed to Spiff Arena.