Before workflows run automated, the process needs to be described in an understandable way. Process modelling is the foundation: who does what, in which order, and when does a decision apply? For a general overview, see process modelling.

Visual mapping in Nuclos

Workflows can be modelled visually in Nuclos. Processes are displayed graphically and structured through a drag-and-drop editor. Individual process steps, decision rules, and responsibilities are clearly defined. The result is a flow that stays understandable for decision-makers and business units alike.

Typical elements of a model:

• individual work steps and their order
• branches and approval rules (for example, from which amount onward)
• roles and responsibilities per step
• dependencies on business objects (order, invoice, item)

From model to implementation

Modelling answers questions that otherwise stay implicit in day-to-day work: who approves? What happens on rejection? What data does the next step need?

Only once these points are clarified does automating the process in the ERP pay off. Starting without a model just digitises existing chaos. Good pilot processes are regular, multi-stage, and clearly rule-based. Quote approval or invoice checking are typical starting points.

Expand after the pilot, not before modelling everything. Next step: process automation and tasks.