BPMN 2.0 - Business Process Model and Notation Innovator for
OutSystems - Agile Platform - Process Notation Reference for BPMN Practitioners
2
' 2001-2009 OutSystems - All rights reserved Page 1 www.outsystems.com TECHNICAL NOTE OutSystems Agile Platform Notation Reference for BPMN Practitioners Agile Platform 5.0 brings with it the ability to design and execute business processes with 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 Plain Start Event Start, initiates the process. Plain End Event End, finishes a process flow. The process may continue in parallel flows. Terminate Event End with Terminate property set to Yes , ends all flows of the process. Start Event with a catching trigger: Message; Timer; Conditional; Signal or Multiple Conditional Start, initiates an alternative flow and may be triggered by a DB event or an explicit API call. Intermediate Event with a catching trigger: Message; Timer; Conditional; Signal or Multiple Wait, pauses the flow waiting for a timeout, a DB event, an API call or for a custom business logic returning true. Intermediate Event with a throwing trigger: Message; Signal or Multiple 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. Task of type: Service, Script or Send (if not email) Automatic Activity, performs custom business logic in the application or in external systems. Task of type: User or Manual 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. Task of type: Receive Wait, for the Receive semantics the application should call the Close Wait API when a message is received.
-
Upload
wilfred-alvarez -
Category
Documents
-
view
33 -
download
5
description
Guide to Outsystems
Transcript of OutSystems - Agile Platform - Process Notation Reference for BPMN Practitioners
© 2001-2009 OutSystems - All rights reserved Page 1 www.outsystems.com
TECHNICAL NOTE
OutSystems Agile Platform Notation Reference for BPMN Practitioners
Agile Platform 5.0 brings with it the ability to design and execute business processes with 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
Plain Start Event
Start, initiates the process.
Plain End Event
End, finishes a process flow. The process may continue in parallel flows.
Terminate Event
End with Terminate property set to Yes, ends all flows of the process.
Start Event with a catching trigger: Message; Timer; Conditional; Signal or Multiple
Conditional Start, initiates an alternative flow and may be triggered by a DB event or an explicit API call.
Intermediate Event with a catching trigger: Message; Timer; Conditional; Signal or Multiple
Wait, pauses the flow waiting for a timeout, a DB event, an API call or for a custom business logic returning true.
Intermediate Event with a throwing trigger: Message; Signal or Multiple
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.
Task of type: Service, Script or Send (if not email)
Automatic Activity, performs custom business logic in the application or in external systems.
Task of type: User or Manual
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.
Task of type: Receive
Wait, for the Receive semantics the application should call the Close Wait API when a message is received.
© 2001-2009 OutSystems - All rights reserved Page 2 www.outsystems.com
Task of type: Send (for email)
Send Email, sends a specified email message in the process flow.
Reusable Sub-Process
Execute Process, runs a sub-process. The parent process only proceeds after all flows of the sub-process finish.
Exclusive Data-Based Decision (Gateway)
Decision, directs to one outgoing gates based on custom business logic.
Sequence Flow Connector, defines the execution order of activities in the flow.
Parallel Split (Fork)
Fork, two or more outgoing connectors (except when starting from a Decision) divide the flow into parallel paths.
Fork and Join using a Parallel Gateway
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 sub-process have ended.
Text Annotation
Comment, can be used to annotate any element or area of the process model.
Additional Information Agile Platform 5.0 Business Process Technology Help http://www.outsystems.com/help/servicestudio/5.0/default.htm#Designing_Processes/Overview_of_Designing_Processes.htm
OMG Business Process Model and Notation (BPMN) Version 1.2 http://www.omg.org/spec/BPMN/1.2/PDF
or
For more information
If you would like to have more information about OutSystems and its products please contact our regional offices:
OutSystems US 2603 Camino Ramon, Suite 200 San Ramon - California 94583, USA Tel: +1 925 242 25 12 Fax: +1 925 242 28 98 [email protected]
OutSystems Benelux Planetenbaan 16 3606 AK Maarssen, The Netherlands Tel: +31(0) 346 583 000 Fax: +31(0) 346 590 201 [email protected]
OutSystems Portugal Rua Central Park 6, 2A 2795-242 Linda-a-Velha, Portugal Tel: +351 21 4153730 Fax: +351 214153731 [email protected]
