Model data flows

The data flow of an executable process step in Process Governance is described using a Data flow diagram. It has exactly one superior object from the control flow. This means that for objects that have multiple object occurrences in a business model, each of these object occurrences has its own data flow diagram.

If a user is explicitly mapped in a data flow, the user's password must also be mapped and must be correct. If the password or user information is missing, the arisservice user is used regardless of whether his password has been changed or not.

Topics

Activate data type check

Create data flow

Open data flow

Model data flow

Update data flow

Show object usage

Consolidate objects in the data flow

Copy object with connected objects and data flow

Open associated data flow

Create changing message contents

Restrict users for task delegation

Model password input for human task

Create data flow for recurring task

Define language for services

Hide/Show unused data fields

Align connections in the data flow

Control the naming or description of a task

Find unused data

Model input tables

Delete data flow

Model variables

Model constants

Place operator

Start report 'Check consistency of data flow dependencies'

Good to know

Data types in data flows

Operators