Skip to main content

 

 

 

Template:OutSystems/Documentation_KB/Breadcrumb_New_Layout

 

 

Template:OutSystems/OSLanguageSwitcher

 

 

 

OutSystems

Notation Reference for BPMN Practitioners

Template:OutSystems/Documentation_KB/ContentCollaboration
  • Edit
    Collaborate with us
    Edit this page on GitHub
  • 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 Description OutSystems Business Process Technology Description
    image alt text Plain Start Event image alt text Start, initiates the process.
    image alt text Plain End Event image alt text End, finishes a process flow. Theprocess may continue in parallelflows.
    image alt text Terminate Event image alt text End with Terminate property set to Yes, ends all flows of the process.
    image alt text Start Event with a catching trigger: Message; Timer; Conditional; Signal or Multiple image alt text Conditional Start, initiates an alternative flow and may be triggered by a DB event or an explicit API call.
    image alt text Intermediate Event with a catching trigger: Message; Timer; Conditional; Signal or Multiple image alt text Wait, pauses the flow waiting for a timeout, a DB event, an API call or for a custom business logic returning true.
    image alt text Intermediate Event with a throwing trigger: Message; Signal or Multiple image alt text Automatic Activity, can be used to broadcast an event (via DB) or call an API to deliver an event to a specific activity or process.
    image alt text Task of type: Service, Script or Send (if not email) image alt text Automatic Activity, performs custom business logic in the application or in external systems.
    image alt text Task of type: User or Manual image alt text Human Activity, waits for a user or group to complete the given task.This activity shows up in the taskbox of one or more users.
    image alt text Task of type: Receive image alt text Wait, for the Receive semantics the application should call the Close Wait API when a message is received.
    image alt text Task of type: Send (for email) image alt text Send Email, sends a specified email message in the process flow.
    image alt text Reusable Sub-Process image alt text Execute Process, runs a subprocess. The parent process only proceeds after all flows of the subprocess finish.
    image alt text Exclusive Data-Based Decision (Gateway) image alt text Decision, directs to one outgoing gates based on custom business logic.
    image alt text Exclusive Data-Based Decision (Gateway) image alt text Connector, defines the execution order of activities in the flow.
    image alt text Parallel Split (Fork) image alt text Fork, two or more outgoing connectors (except when starting from a Decision) divide the flow into parallel paths.
    image alt text Fork and Join using a Parallel Gateway image alt text Fork 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.
    image alt text Text Annotation image alt text Comment, can be used to annotate any element or area of the process model.
    • Was this article helpful?