Usage of explicit joins before activities
Joins should be modeled explicitly using gateways. This is important for clarity and legibility of diagrams. read more
Conventions:
Fields:
Joins should be modeled explicitly using gateways. This is important for clarity and legibility of diagrams. read more
Elements that represent similar frequent activities or tasks should be defined as a dictionary items in Signavio Process Manager. This way, the activity can be updated for all diagrams at … read more
An activity requires a name. The activity’s label should shortly describe the Task that has to be performed. read more
Use a limited number of activities in process models to ensure clarity and comprehensibility. read more
For a clear process, an or-split requires a preceding task. read more
At least one (expanded) pool should be modeled, and at least one activity should be modeled within this pool. read more
An activity can be interpreted in several ways. To make sure that the activity is understood properly, a description should be given. read more
An activity or task should be named after the process step which has to be executed. To keep your process landscape clear and easily comprehensible, all the activities within a process … read more