Skip to content

Steps and step details

Steps are the building blocks of an Oroko process map.

A step can describe the work itself and carry the context needed to understand how that work is performed.

Oroko supports these canonical step types:

  • Start
  • Activity
  • Decision
  • Subprocess
  • End

Start and End identify process boundaries. Activities describe work. Decisions represent branching points. Subprocesses can represent a lower-level flow.

Depending on the step, Oroko can capture:

  • name;
  • description;
  • owner;
  • role;
  • system;
  • duration;
  • inputs;
  • outputs;
  • documents;
  • notes;
  • annotations.

Use these fields to make the step understandable without turning the visual node itself into a large block of text.

A document can be listed against a step. Oroko also supports attaching files to a selected step.

The current file attachment flow accepts DOCX, PNG, PDF, CSV, JSON, Markdown, XLS and XLSX files up to 25 MB.

A Subprocess step can contain a child flow.

Use a subprocess when a step needs its own lower-level sequence while the parent process should remain readable at a higher level.

Start and End steps cannot be deleted.

Deleting another step removes that step and its related connections. Other downstream steps remain unless they are separately removed.