Elements in Noreja Process Graphs

Learning to read the visual grammar speeds up insight generation. Standard activities appear as dark‑blue rectangles, whereas divergent or convergent nodes stretch wider to signal branching logic. A batching symbol indicates that cases were collected before moving on, and change activities show where data was altered without progressing the flow. Expected start and end points are turquoise circles; red‑ringed circles reveal unexpected entry or exit events and often merit closer inspection. For a more details explaination, let's start with the activity elements:

• Process activity: The [bluish diamond with rounded corners] represents a process activity. A process activity represents a clearly definable activity that is executed in the course of the end-to-end process. Process activities with this symbol do not experience convergent or divergent object behavior (1:1 cardinality). This means that the same number of business objects flows in as input as flows out in the process activity.
• Divergent process activity: The [blue object with rounded edges that looks like an arrow pointing to the left] represents a process activity with divergent object behavior. This means that multiple business objects flow out of a this one process activity as output (1:n cardinality).
• Convergent process activity: The [blue object with rounded edges that looks like an arrow pointing to the right] represents a process activity with convergent object behavior. This means that several business objects flow as input into this one process activity (n:1 cardinality).
• Con/div process activity: The [blue and from both sides dented object with rounded corners] represents a process activity with divergent and convergent object behavior (n:m cardinality): 1) Multiple objects from a previous process activity converge in this process activity. 2) An object of this process activity splits into several objects of a subsequent process activity.
• Batching activity: The [hexagonal blue object with rounded corners] represents a process activity embedded in the overall business process where bundling behavior occurs. In this case, activities from separate process instances (different dimension keys) are processed in combination and stored in a common business object.
• Change activity: The [dark gray diamond with rounded corners] represents a random activity that cannot be sorted into the causal order of the process. The special characteristics here is that this activity type can only be connected to the main process flow with a suspended path.
• Omitted activity: The [grayed out diamond with rounded corners and a solid border] represents a process activity that was not recorded but should actually have been mandatory. Since it is a purly hypothetical behavior, no specific cardinality is indicated.
• Optional activity: The [grayed out diamond with rounded corners and a dashed border] represents a process activity that was not recorded but would be optionally executable. Since it is a purly hypothetical behavior, no specific cardinality is indicated.

In Noreja, we differentiate also between different path semantics. Here are the detailed descriptions of the meanings behind the elements:

• Conformance path: The [dark gray solid and square arrow] symbolizes a so-called conformance path. This means that the observed process flow also corresponds to that of the causal order. The thicker the arrow, the more process instances flow through it.
• Violation path: The [red and rounded arrow] represents a violation from the defined process dimension. This is therefore behavior that was recorded in the data but is highly unlikely to be desired.
• Hypothetical path: The [light gray dashed and square arrow] symbolizes a so-called hypothetical path. These paths symbolize the expected causal order of the process. The actual course of the process, on the other hand, could not be observed here, so it did not take place in reality.
• Omitted path: The [light gray dashed path with a blank arrowhead] symbolizes a so-called omitted path. The intended sequence flow is considered mandatory, but with no data recorded that confirms its execution. The actual course of the process, on the other hand, could not be observed here, so it did not take place in reality.

Finally, there are also differantiations between start and end points in the process. In fact, we visualize expected starts with turquoise and unexpected starts in red: Moreover, there are final start and end points but also intermediate ones. 

• Expected process start/end: The [round turquoise circle] symbolizes a process start or end of a process instance. If the arrowhead of a path runs into the circle, it is a process end. In the opposite case it is a process start.
• Unexpected start/end: The [round red circle] symbolizes an unexpected process start or end of a process instance. If the arrowhead of a path runs into the circle, it is a process end. In the opposite case it is a process start.
• Expected intermediate start/end: The [turquoise triangle] symbolizes an intermediate start or end, where individual business objects are added or removed in the course of a running process instance. If the arrowhead of a path runs into the triangle, it is an intermediate end. In the opposite case, it is an intermediate start.
• Unexpected intermediate start/end: The [red triangle] symbolizes an unexpected intermediate start or end, where individual business objects are added or removed in the course of a running process instance. If the arrowhead of a path runs into the triangle, it is an intermediate end. In the opposite case, it is an intermediate start.

Clicking any element activates it with a turquoise outline and scrolls the Details panel into view. Here you find rich statistics: average, median, minimum, and maximum cycle times; behavioural measures such as loops or rework; and every case property that the import contained. This evidence base is invaluable for hypothesis validation—whether you are benchmarking regional performance or confirming the root cause of a compliance breach.