BPMN - Tutorial Style: Default Style: Accent 2 Call Activity Styles All BPMN gallery items has styles support so the shapes will follow the Default and Accent 2 style from your draw/impress template. Users can change the BPMN diagram by edit Default and Accent 2 style. Direct formatting BPMN gallery items use 11px font size to fit well in writer and draw. Bold borders have 0,10 mm line width. Grid As all LibreOffice gallery items the BPMN symbols fit perfect into the default grid - 1x1 cm with 4 subsections - 0.5x0.5‘‘ with 5 subsections BPMN gallery gallery items store the styles as direct formatting style, so when you move an gallery item into the page click Format → Clear Direct Formatting and the gallery items use the defined styles. Style Examples you can play around with Default and Accent 2 style to get nice symbols for example Items fetched Order Delivered Price > 100 Exclusive Gateway (XOR) Parallel Gateway (AND) Payment Failed Event Based Gateway Payment Details Updated 1 hour BPMN - Examples start-event-none Ship Parcel end-event-none Ship Parcel with Transport Insurance Order Ready Order Complete start-event-none Process Payment end-event-none Ship Parcel end-event-none end-event-none start-event-none Cancel Order Process Payment Order Request Order Fulfilled [Material need to be ordered] Customer Answer [Invoice needs to be updated] Order Process Register Order Subprocess BPMN - Examples Register Order Prepare Documents for Shipment Make a Plan for Manufacturing Produce Ordered Items Purchase Requested Materials Collect Order Ship Order end-event-none Prepare Invoice Update Invoice Send Invoice to Customer Process Payment Register Order in Manufacturing System end-event-none BPMN - Events None: Untyped events, indicate start point, state of changes or final states Message: Receiving and sending messages Timer: Cyclic timer events, points in time, time spans, or timeouts Escalation: Escalating to a higher level of responsibility Conditional: Reacting to changed business conditions or integrating business rules Link: Off-page connectors. Two corresponding link events equal a sequence flow Error: Catching or throwing named errors Cancel: Reacting to cancelled transactions or triggering cancellations Compensation: Handling or triggering compensation Signal: Signaling across diff. processes. A signal thrown can be caught multiple times Multiple: Catching one out of a set of events. Throwing all events defined Parallel Multiple: Catching all out of a set of parallel events Terminate: Triggering the immediate termination of a process Event Sub-Process Interrupting Top-Level Standard Catching Throwing Standard Event Sub-Processing Non-interrupting Boundary Non-Interrupting Boundary Interrupting Start Intermediate End start-event-none end-event-none Exclusive (XOR) Split: routes sequence flow to a precise outgoing branch. Merge: waits for one incoming branch to finish before triggering an otugoing flow. A gateway is represented with a diamond shape and determines forking and merging of paths, depending on the conditions expressed. Inclusive (OR/AND) One or more branches are activated when splitting. All active incoming branches must complete before merging. Parallel (AND) When splitting sequence flow: outgoing branches are initiated simultaneously. When merging parallel branches: the gateway waits for all incoming branches to finish before triggering outgoing flow Complex Gateways that represent actions not capture by other gateways. Can be complex, merging or branching actions/behaviors. Exclusive Event Based Each occurrence of a subsequent event starts a new process instant. Parallel Event Based Two parallel processes are started based on an event, but there is no evaluation of the event. Event Based The condition determining the path of a process is based on an evaluated event. BPMN - Gateway Parallel Fork Parallel Join XOR Decision Condition 1 Default OR Decision Condition 1 Condition 2 OR Merge Complex Merge Complex Decision Message Task Task Task Transaction Event- SubProcess Call Activity send receive user manual business rule service script sub-process loop parallel ad-hoc compensation sequential Group Task is an atomic activity within a process flow. A task is used when the work in a process cannot be broken down into finer levels of detail Transaction is a specialized type of sub-process whose special behavior is controlled through a transaction protocol. Event SubProcess may occur many times. Unlike the standard SubProcess that uses the flow of the parent process as a trigger, it has a Start Event as a trigger. Group is used to group different activities but does not affect the flow in the diagram Call Activity identifies a point in a process where a global process is used. The Call Activity acts as a ‘wrapper’ for the invocation of the global process within the execution. Activity Markers indicate executive behaviour of activities. Task Types specify the nature of the action to be preformed. Text Annotation BPMN - Activities Subtask Data Object element can optionally reference a Data State element, which is the state of data contained in a Data Object Data Input is an external input for the whole process Data Output is a data result of the whole process Data Store provides a mechanism for activities to retrieve or update stored information that will persist beyond the scope of a process Collection Data Object represents collections of information BPMN - Data