Skip to main content
OutSystems

Notation Reference for BPMN Practitioners

OutSystems allows designing and executing business processes through the Business Process Technology Add-on. This technical note describes the notation used for Process Modeling targeted at practitioners currently modeling processes using BPMN.

BPMN 1.2 OutSystems Business Process Technology
11.pngPlain Start Event 12.jpgStart, initiates the process.
21.pngPlain End Event 22.jpgEnd, finishes a process flow. The
process may continue in parallel
flows.
31.pngTerminate Event 32.jpgEnd with Terminate property set to Yes, ends all flows of the process.
41.pngStart Event with a catching trigger: Message; Timer; Conditional; Signal or Multiple 42.jpgConditional Start, initiates an alternative flow and may be triggered by a DB event or an explicit API call.
51.pngIntermediate Event with a catching trigger: Message; Timer; Conditional; Signal or Multiple 52.jpgWait, pauses the flow waiting for a timeout, a DB event, an API call or for a custom business logic returning true.
611.jpg612.jpg613.jpgIntermediate Event with a throwing trigger: Message; Signal or Multiple 62.jpgAutomatic Activity, can be used to broadcast an event (via DB) or call an API to deliver an event to a specific activity or process.
71.pngTask of type: Service, Script or Send (if not email) 72.jpgAutomatic Activity, performs custom business logic in the application or in external systems.
71.pngTask of type: User or Manual 82.jpgHuman Activity, waits for a user or group to complete the given task.
This activity shows up in the taskbox of one or more users.
71.png Task of type: Receive 92.jpgWait, for the Receive semantics the application should call the Close Wait API when a message is received.
71.pngTask of type: Send (for email) 10.2.jpgSend Email, sends a specified email message in the process flow.
Reusable Sub-Process11.1.png 11.2.jpgExecute Process, runs a subprocess. The parent process only proceeds after all flows of the subprocess finish.
12-1.png Exclusive Data-Based Decision (Gateway) 12.2.jpgDecision, directs to one outgoing gates based on custom business logic.
12.1.pngSequence Flow 13.2.jpgConnector, defines the execution order of activities in the flow.
13.1.jpgParallel Split (Fork) 14.2.jpgFork, two or more outgoing connectors (except when starting from a Decision) divide the flow into parallel paths.
14.1.jpgFork and Join using a Parallel Gateway 15.2.pngFork and Join, is implemented by calling a sub-process with the two or more parallel paths that must be joined. The parent process only proceeds after all flows of the subprocess have ended.
15.1.pngText Annotation 16.2.pngComment, can be used to annotate any element or area of the process model

 

  • Was this article helpful?