https://www.workplace.enterpriseplus.tools/api.php?action=feedcontributions&feedformat=atom&user=Fbajohr 2026-04-17T08:51:49Z User contributions MediaWiki 1.24.2 https://www.workplace.enterpriseplus.tools/index.php?title=Objects:X-BPMN_Notations&diff=1330 2015-08-31T13:41:46Z

<p>Fbajohr: </p> <hr /> <div>&lt;div class=&quot;row&quot;&gt;<br /> <br /> &lt;div class=&quot;col-md-3 nopadding&quot;&gt; <br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''TASK TYPES'''<br /> &lt;/div&gt;<br /> &lt;div class=&quot;no-left-padding&quot; style=&quot;margin-top: 10px;&quot;&gt;<br /> <br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Send-01.png | 30px | alt=Send]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Send Task'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Receive-01.png | 30px | alt=Receive]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Receive Task'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:User Task-01.png | 30px | alt=User]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''User Task'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Manual Task-01.png | 30px | alt=Task]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Manual Task'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Service-01.png | 30px | alt=Service]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Manual Service Task'''&lt;/span&gt;<br /> :A Manual Service is when the service is performed by a human.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Automated Service-01.png | 30px | alt=Service]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Automated Service Task'''&lt;/span&gt;<br /> :An Automated Service can be either an application service, data service, platform service, infrastructure service or a web service.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Automated Task-01.png | 30px | alt=Activity]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Automated Task'''&lt;/span&gt;<br /> :An Automated Task is an activity that is automated through either a business process execution engine or any application (e.g. using application features and/or functions to enable the application task).<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Business Rule Task-01.png | 30px | alt=Rule]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Business Rule Task'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Reporting-01.png | 30px| alt=Reporting ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Reporting Task'''&lt;/span&gt;<br /> :Reporting is the exposure, description and portrayment of specific tasks, services and the associated information and data.The information and data objects/source can bind with the reporting activity the process components to the specific cockpits,dashboards or scorecards.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Mapping-01.png | 30px | alt=Mapping]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Mapping Task'''&lt;/span&gt;<br /> :Mapping activities includes identifying, defining and plotting the involved business, information and data objects within theactivities. This allows to identify possible grouping of common business, information and data objects and their associatedrules (e.g. rulesets), enabling the change of complex objects and views into more simple views.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Decision Table-01.png | 30px| alt=Table ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Decision Table'''&lt;/span&gt;<br /> :A Decision Table defines decisions based on a number of given conditions and actions. Decision tables allow to work from the same information, and are therefore a precise way to model complicated logics and associations.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Notification-01.png | 30px | alt=Notification]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Notification Task'''&lt;/span&gt;<br /> :An instance of a message delivered to one or more recipients. A Notification activity sends a message to a user, both therecipients and the content that needs to be specified. Notification activities furthermore allow flow rulesets to be applied inorder to notify users of events that occur during the workflow.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Script Task-01.png | 30px | alt=Script]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Script Task'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Rule-01.png | 30px | alt=Rule]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Rule'''&lt;/span&gt;<br /> :A Rule is a statement describing a business policy or decision procedure. Some programming languages run business rules together in very complex algorithms. In business process analysis, each rule is usually stated independently, in the general format of: If A and B, Then C.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - RuleScript-01.png | 30px | alt=RuleScript]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Rule Script'''&lt;/span&gt;<br /> :A Rule Script allows generating a rule in a scripting environment. This is done through the connection of other activities andthe rules that govern these relations, and the actions between them. Rule scripts can furthermore be used with script types,and thereby automated test rules (e.g. configurable, programmed, query and event-based network alerts). The link betweenrule scripts and the mentioned script type could be used as template–based query that can be run against backend tables ordatabase views.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - RuleSet-01.png | 30px | alt=RuleSet]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Ruleset'''&lt;/span&gt;<br /> :A Ruleset is a collection (and thereby a grouping) of rules. They are either grouped based on common related rules, decisions tables or the need to govern a specific set or behavior of tasks. Grouping such rulesets allows for sharing of rules and execution by a rules engine.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Rule Flow-01.png | 30px | alt=Rule Flow]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Rule Flow'''&lt;/span&gt;<br /> :Rule Flows are comprised of linked tasks that contain the instructions for which rules to execute and in what order. The rulesare organized into tasks, and the rule flow specifies how tasks are chained together; how, when, and under what conditionsthey are executed. When you are dealing with many large rulesets, managing the order in which rules are evaluated canbecome complex. Rule flows allows you to specify the order in which rulesets are to be evaluated. It does so by providing youwith a flow chart. Use this chart to define which rule sets should be evaluated in sequence, and which ones in parallel, and tospecify conditions under which rule sets should be evaluated. The reuse of rules components and their natural relations likeactivity association are an important aspect of rule modelling principles. This allows for rule modelling consistency betweenthe different rule artifacts from the rule flows, rule scripts, rulesets, flow rulesets, rules and decision tables.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Flow Ruleset-01.png | 30px | alt=Flow Ruleset]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Flow Ruleset'''&lt;/span&gt;<br /> :A Flow Ruleset is a collection (and thereby grouping) of rules that apply to a flow. These flow rulesets are either grouped based on common related rules in the flow, decisions tables, or the need to govern a specific set or behavior of tasks in the flow. Grouping such flow rulesets allows for sharing of rules and execution, by a rule engine throughout the entire flow. As well as the relation to the reuse of such rulsets in other flows, starting from the main flow where the ruleset are applied.<br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;col-md-3&quot;&gt; <br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''MARKERS'''<br /> &lt;/div&gt;<br /> &lt;div class=&quot;&quot; style=&quot;margin-top: 10px;&quot;&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Sub-process Marker-01.png | 30px | alt=Sub-process Marker]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Sub-process Marker'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Loop-01.png | 30px | alt=Loop Marker]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Loop Marker'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Parallel Multiple Instance-01.png | 30px | alt=Parallel MI Marker]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Parallel MI Marker'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Sequential Multiple Instance-01.png | 30px | alt=Sequential MI Marker]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Sequential MI Marker'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image: Ad Hoc Marker-01.png | 30px | alt='Ad Hoc Marker]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Ad Hoc Marker'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Compensation-01.png | 30px| alt=Compensation ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Compensation'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;&lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Annotation-01.png | 30px | alt=Annotation Marker']]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Annotation Marker'''&lt;/span&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;&quot; style=&quot;margin-top: 10px;&quot;&gt;<br /> <br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''FLOWS'''<br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;media-notations&quot; style=&quot;margin-top:10px;&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Sequence Flow-01.png | 30px | alt=Sequence Flow]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Sequence Flow'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot; style=&quot;margin-top:10px;&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Conditional Flow-01.png | 30px | alt=Conditional flow]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Conditional Flow'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot; style=&quot;margin-top:10px;&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Default Flow-01.png | 30px | alt=Default flow]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Default Flow'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Message Flow-01.png | 30px | alt=Message Flow]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Message Flow'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Association Flow-01.png | 30px | alt=Association Flow]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Association Flow'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Data Association Flow-01.png | 30px | alt=Data Association Flow]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Data Association Flow'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> <br /> <br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;col-md-3 nopadding&quot;&gt; <br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''OBJECTS'''<br /> &lt;/div&gt;<br /> &lt;div class=&quot;no-left-padding&quot; style=&quot;margin-top: 10px;&quot;&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Business Object-01.png | 30px | alt=Business Object]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Business Object'''&lt;/span&gt;<br /> :A Business Object is the term used to express real-world objects like people, employee, products or a sales order, customerand revenue. Business Objects used for example in business, process and service mapping and furthermore used in applicationimplementations where they are used as a patented semantic layer that shields users from the complexities of informationtable names and data relationships.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Business Store-01.png | 30px | alt=Business Store]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Business Store'''&lt;/span&gt;<br /> :Is a place where the real-world objects are stored.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Business Input-01.png | 30px | alt=Business Input]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Business Input'''&lt;/span&gt;<br /> :Is an external input for the real-world objects. A kind of input parameter.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Business Output-01.png | 30px| alt=Business Output ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Business Output'''&lt;/span&gt;<br /> :Is the real-world result of the entire process and or service flow. A kind of output parameter.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Collection of Business Objects-01.png | 30px | alt=Collection of Business Objects]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Collection of Business Objects'''&lt;/span&gt;<br /> :Represents a collection of real-world objects, e.g. a employee roles.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Information Object-01.png | 30px | alt=Information Objects]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Information Objects'''&lt;/span&gt;<br /> :An Information Object is used to specify information about real-world objects (like people, employees, products or a salesorder, etc.), and is therefore a digital representation of an existing entity within an Information System (e.g. Oracle ERP or SAPERP). It encompasses both the business information (in the form of functions and methods) and the application information(in the form of attributes) of the entity. Information Objects can be found and therefore modeled in business functions,business services and business processes.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Information Input-01.png | 30px | alt=Information Input]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Information Input'''&lt;/span&gt;<br /> :Is an external information input for the entire process. A kind of input parameter.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Information Output-01.png | 30px ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Information Output'''&lt;/span&gt;<br /> :Is the information output/result of the entire process. A kind of output parameter.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Information Store-01.png | 30px | alt=Information Store]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Information Store'''&lt;/span&gt;<br /> :Is a place where the information can be read or written (e.g. knowledge management or a filingcabinet). It persists beyond the lifetime of the process instance.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Collection of Information Objects-01.png | 30px | alt=Collection of Information Objects]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Collection of Information Objects'''&lt;/span&gt;<br /> :Represents a collection of information (e.g. a list of order items).<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Data Objects - Data Object-01.png | 30px | alt=Data Object]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Data Object'''&lt;/span&gt;<br /> :A Data Object is a logical cluster of all tables in the data set that have one or more columns containing data related to the same business entity. Data objects are not maps, but instead represent an object view of related Information Objects and they represent Business Objects.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Data Objects - Data Input-01.png | 30px | alt=Data Input]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Data Input'''&lt;/span&gt;<br /> :Is an external data input for the entire process. A kind of input parameter.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Data Objects - Data Output-01.png | 30px | alt=Data Output]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Data Output'''&lt;/span&gt;<br /> :Is the data result of the entire process. A kind of output parameter.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Data Objects - Data Store-01.png | 30px | alt=Data Store]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Data Store'''&lt;/span&gt;<br /> :Is a place where the process can read or write data (e.g. a database or a filing cabinet). It persists beyond the lifetime of the process instance.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Data Objects - Collection of Data Objects-01.png | 30px | alt=Collection of Data Objects]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Collection of Data Objects'''&lt;/span&gt;<br /> :Represents a collection of data tables/columns containing data related to the same data entity (e.g. a list of order items).<br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> <br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;col-md-3&quot;&gt; <br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''EVENTS'''<br /> &lt;/div&gt;<br /> &lt;div class=&quot;&quot; style=&quot;margin-top: 10px;&quot;&gt;<br /> <br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Timer-01.png | 30px | alt=Send Timer]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Send Timer'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Escalation (Start)-01.png | 30px| alt=Escalation (start) ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Escalation (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Escalation (End)-01.png | 30px| alt=Escalation (end) ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Escalation (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Link (Standard)-01.png | 30px | alt=Link (start)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Link (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Link (End)-01.png | 30px | alt='Link (end)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Link (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Error (Start)-01.png | 30px | alt=Error (start)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Error (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Error (End)-01.png | 30px| alt=Error (end)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Error (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Cancel (Standard)-01.png | 30px | alt=Cancel (start)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Cancel (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Cancel (End)-01.png | 30px | alt=Cancel (end)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Cancel (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Conditional-01.png | 30px | alt=Conditional]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Conditional'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Compensation (Start)-01.png | 30px | alt=Compensation (start)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Compensation (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Compensation (End)-01.png | 30px | alt=Compensation (end)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Compensation (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Signal (Standard)-01.png | 30px | alt=Signal (start)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Signal (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Signal (End)-01.png | 30px | alt=Signal (end)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Signal (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Multiple (Standard)-01.png | 30px | alt=Multiple (start)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Multiple (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Multiple (End)-01.png | 30px | alt=Multiple (end)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Multiple (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Parallel Multiple-01.png | 30px| alt=Parallel Multiple ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Parallel Multiple'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Terminate-01.png | 30px| alt=Terminate ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Terminate'''&lt;/span&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> <br /> &lt;/div&gt;<br /> &lt;div class=&quot;row&quot; style=&quot;margin-top: 10px; margin-bottom: 50px;&quot;&gt;<br /> &lt;div class=&quot;col-md-3 nopadding&quot;&gt;<br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''GATEWAYS'''<br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;media-notations&quot; style=&quot;margin-top: 10px;&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Gateway-01.png | 30px | alt=Gateway]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Event-based Gateway-01.png | 30px | alt=Event-based Gateway]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Event-based Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Inclusive Gateway-01.png | 30px | alt=Inclusive Gateway]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Inclusive Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Exclusive Gateway-01.png | 30px | alt=Exclusive Gateway]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Exclusive Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Exclusive Event-based Gateway-01.png | 30px | alt=Exclusive Event-based Gateway]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Exclusive Event-based Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Parallel Gateway-01.png | 30px | alt=Parallel Gateway]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Parallel Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Parallel Event-based Gateway-01.png | 30px| alt=Parallel Event-based Gateway ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Parallel Event-based Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Complex Gateway-01.png | 30px| alt=Complex Gateway ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Complex Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div class=&quot;col-md-3&quot;&gt;<br /> <br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''CONVERSATIONS'''<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot; style=&quot;margin-top: 10px;&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Multiple (Standard)-01.png | 30px ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''A Conversation'''&lt;/span&gt;<br /> :defines a set of logically related message exchanges. When market with a '''(+)''' symbol it indicates a Sub-Conversation, a compound conversation element.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Multiple (Standard)-01.png | 30px | alt=A Call Conversation]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''A Call Conversation'''&lt;/span&gt;<br /> :is a wrapper for a globally defined Conversation of Sub-Conversation. A call to a Sub-Conversation is market with a '''(+)''' symbol.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Link-01.png | 30px | alt=A Conversation Link]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''A Conversation Link'''&lt;/span&gt;<br /> :connects Conversations And Participants.<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> [[ Image:XPMN.png |1500px]]<br /> [[Category:Objects]]<br /> {{DISPLAYTITLE:X-BPMN Notations}}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:Data_Association_Flow-01.png&diff=1329 2015-08-31T13:40:29Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:Association_Flow-01.png&diff=1328 2015-08-31T13:39:48Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:Message_Flow-01.png&diff=1327 2015-08-31T13:39:09Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:Sequence_Flow-01.png&diff=1326 2015-08-31T13:37:33Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=Objects:X-BPMN_Notations&diff=1323 2015-08-31T13:21:38Z

<p>Fbajohr: </p> <hr /> <div>&lt;div class=&quot;row&quot;&gt;<br /> <br /> &lt;div class=&quot;col-md-3 nopadding&quot;&gt; <br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''TASK TYPES'''<br /> &lt;/div&gt;<br /> &lt;div class=&quot;no-left-padding&quot; style=&quot;margin-top: 10px;&quot;&gt;<br /> <br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Send-01.png | 30px | alt=Send]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Send Task'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Receive-01.png | 30px | alt=Receive]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Receive Task'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:User Task-01.png | 30px | alt=User]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''User Task'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Manual Task-01.png | 30px | alt=Task]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Manual Task'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Service-01.png | 30px | alt=Service]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Manual Service Task'''&lt;/span&gt;<br /> :A Manual Service is when the service is performed by a human.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Automated Service-01.png | 30px | alt=Service]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Automated Service Task'''&lt;/span&gt;<br /> :An Automated Service can be either an application service, data service, platform service, infrastructure service or a web service.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Automated Task-01.png | 30px | alt=Activity]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Automated Task'''&lt;/span&gt;<br /> :An Automated Task is an activity that is automated through either a business process execution engine or any application (e.g. using application features and/or functions to enable the application task).<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Business Rule Task-01.png | 30px | alt=Rule]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Business Rule Task'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Reporting-01.png | 30px| alt=Reporting ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Reporting Task'''&lt;/span&gt;<br /> :Reporting is the exposure, description and portrayment of specific tasks, services and the associated information and data.The information and data objects/source can bind with the reporting activity the process components to the specific cockpits,dashboards or scorecards.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Mapping-01.png | 30px | alt=Mapping]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Mapping Task'''&lt;/span&gt;<br /> :Mapping activities includes identifying, defining and plotting the involved business, information and data objects within theactivities. This allows to identify possible grouping of common business, information and data objects and their associatedrules (e.g. rulesets), enabling the change of complex objects and views into more simple views.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Decision Table-01.png | 30px| alt=Table ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Decision Table'''&lt;/span&gt;<br /> :A Decision Table defines decisions based on a number of given conditions and actions. Decision tables allow to work from the same information, and are therefore a precise way to model complicated logics and associations.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Notification-01.png | 30px | alt=Notification]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Notification Task'''&lt;/span&gt;<br /> :An instance of a message delivered to one or more recipients. A Notification activity sends a message to a user, both therecipients and the content that needs to be specified. Notification activities furthermore allow flow rulesets to be applied inorder to notify users of events that occur during the workflow.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Script Task-01.png | 30px | alt=Script]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Script Task'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Rule-01.png | 30px | alt=Rule]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Rule'''&lt;/span&gt;<br /> :A Rule is a statement describing a business policy or decision procedure. Some programming languages run business rules together in very complex algorithms. In business process analysis, each rule is usually stated independently, in the general format of: If A and B, Then C.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - RuleScript-01.png | 30px | alt=RuleScript]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Rule Script'''&lt;/span&gt;<br /> :A Rule Script allows generating a rule in a scripting environment. This is done through the connection of other activities andthe rules that govern these relations, and the actions between them. Rule scripts can furthermore be used with script types,and thereby automated test rules (e.g. configurable, programmed, query and event-based network alerts). The link betweenrule scripts and the mentioned script type could be used as template–based query that can be run against backend tables ordatabase views.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - RuleSet-01.png | 30px | alt=RuleSet]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Ruleset'''&lt;/span&gt;<br /> :A Ruleset is a collection (and thereby a grouping) of rules. They are either grouped based on common related rules, decisions tables or the need to govern a specific set or behavior of tasks. Grouping such rulesets allows for sharing of rules and execution by a rules engine.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Rule Flow-01.png | 30px | alt=Rule Flow]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Rule Flow'''&lt;/span&gt;<br /> :Rule Flows are comprised of linked tasks that contain the instructions for which rules to execute and in what order. The rulesare organized into tasks, and the rule flow specifies how tasks are chained together; how, when, and under what conditionsthey are executed. When you are dealing with many large rulesets, managing the order in which rules are evaluated canbecome complex. Rule flows allows you to specify the order in which rulesets are to be evaluated. It does so by providing youwith a flow chart. Use this chart to define which rule sets should be evaluated in sequence, and which ones in parallel, and tospecify conditions under which rule sets should be evaluated. The reuse of rules components and their natural relations likeactivity association are an important aspect of rule modelling principles. This allows for rule modelling consistency betweenthe different rule artifacts from the rule flows, rule scripts, rulesets, flow rulesets, rules and decision tables.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Flow Ruleset-01.png | 30px | alt=Flow Ruleset]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Flow Ruleset'''&lt;/span&gt;<br /> :A Flow Ruleset is a collection (and thereby grouping) of rules that apply to a flow. These flow rulesets are either grouped based on common related rules in the flow, decisions tables, or the need to govern a specific set or behavior of tasks in the flow. Grouping such flow rulesets allows for sharing of rules and execution, by a rule engine throughout the entire flow. As well as the relation to the reuse of such rulsets in other flows, starting from the main flow where the ruleset are applied.<br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;col-md-3&quot;&gt; <br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''MARKERS'''<br /> &lt;/div&gt;<br /> &lt;div class=&quot;&quot; style=&quot;margin-top: 10px;&quot;&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Sub-process Marker-01.png | 30px | alt=Sub-process Marker]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Sub-process Marker'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Loop-01.png | 30px | alt=Loop Marker]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Loop Marker'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Parallel Multiple Instance-01.png | 30px | alt=Parallel MI Marker]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Parallel MI Marker'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Sequential Multiple Instance-01.png | 30px | alt=Sequential MI Marker]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Sequential MI Marker'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image: Ad Hoc Marker-01.png | 30px | alt='Ad Hoc Marker]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Ad Hoc Marker'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Compensation-01.png | 30px| alt=Compensation ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Compensation'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;&lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Annotation-01.png | 30px | alt=Annotation Marker']]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Annotation Marker'''&lt;/span&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;&quot; style=&quot;margin-top: 10px;&quot;&gt;<br /> <br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''FLOWS'''<br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;media-notations&quot; style=&quot;margin-top:10px;&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Link-01.png | 30px | alt=Sequence Flow]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Sequence Flow'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot; style=&quot;margin-top:10px;&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Conditional Flow-01.png | 30px | alt=Conditional flow]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Conditional Flow'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot; style=&quot;margin-top:10px;&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Default Flow-01.png | 30px | alt=Default flow]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Default Flow'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Link-01.png | 30px | alt=Message Flow]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Message Flow'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Link-01.png | 30px | alt=Association Flow]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Association Flow'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Link-01.png | 30px | alt=Data Association Flow]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Data Association Flow'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> <br /> <br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;col-md-3 nopadding&quot;&gt; <br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''OBJECTS'''<br /> &lt;/div&gt;<br /> &lt;div class=&quot;no-left-padding&quot; style=&quot;margin-top: 10px;&quot;&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Business Object-01.png | 30px | alt=Business Object]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Business Object'''&lt;/span&gt;<br /> :A Business Object is the term used to express real-world objects like people, employee, products or a sales order, customerand revenue. Business Objects used for example in business, process and service mapping and furthermore used in applicationimplementations where they are used as a patented semantic layer that shields users from the complexities of informationtable names and data relationships.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Business Store-01.png | 30px | alt=Business Store]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Business Store'''&lt;/span&gt;<br /> :Is a place where the real-world objects are stored.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Business Input-01.png | 30px | alt=Business Input]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Business Input'''&lt;/span&gt;<br /> :Is an external input for the real-world objects. A kind of input parameter.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Business Output-01.png | 30px| alt=Business Output ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Business Output'''&lt;/span&gt;<br /> :Is the real-world result of the entire process and or service flow. A kind of output parameter.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Collection of Business Objects-01.png | 30px | alt=Collection of Business Objects]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Collection of Business Objects'''&lt;/span&gt;<br /> :Represents a collection of real-world objects, e.g. a employee roles.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Information Object-01.png | 30px | alt=Information Objects]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Information Objects'''&lt;/span&gt;<br /> :An Information Object is used to specify information about real-world objects (like people, employees, products or a salesorder, etc.), and is therefore a digital representation of an existing entity within an Information System (e.g. Oracle ERP or SAPERP). It encompasses both the business information (in the form of functions and methods) and the application information(in the form of attributes) of the entity. Information Objects can be found and therefore modeled in business functions,business services and business processes.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Information Input-01.png | 30px | alt=Information Input]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Information Input'''&lt;/span&gt;<br /> :Is an external information input for the entire process. A kind of input parameter.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Information Output-01.png | 30px ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Information Output'''&lt;/span&gt;<br /> :Is the information output/result of the entire process. A kind of output parameter.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Information Store-01.png | 30px | alt=Information Store]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Information Store'''&lt;/span&gt;<br /> :Is a place where the information can be read or written (e.g. knowledge management or a filingcabinet). It persists beyond the lifetime of the process instance.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Collection of Information Objects-01.png | 30px | alt=Collection of Information Objects]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Collection of Information Objects'''&lt;/span&gt;<br /> :Represents a collection of information (e.g. a list of order items).<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Data Objects - Data Object-01.png | 30px | alt=Data Object]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Data Object'''&lt;/span&gt;<br /> :A Data Object is a logical cluster of all tables in the data set that have one or more columns containing data related to the same business entity. Data objects are not maps, but instead represent an object view of related Information Objects and they represent Business Objects.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Data Objects - Data Input-01.png | 30px | alt=Data Input]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Data Input'''&lt;/span&gt;<br /> :Is an external data input for the entire process. A kind of input parameter.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Data Objects - Data Output-01.png | 30px | alt=Data Output]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Data Output'''&lt;/span&gt;<br /> :Is the data result of the entire process. A kind of output parameter.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Data Objects - Data Store-01.png | 30px | alt=Data Store]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Data Store'''&lt;/span&gt;<br /> :Is a place where the process can read or write data (e.g. a database or a filing cabinet). It persists beyond the lifetime of the process instance.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Data Objects - Collection of Data Objects-01.png | 30px | alt=Collection of Data Objects]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Collection of Data Objects'''&lt;/span&gt;<br /> :Represents a collection of data tables/columns containing data related to the same data entity (e.g. a list of order items).<br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> <br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;col-md-3&quot;&gt; <br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''EVENTS'''<br /> &lt;/div&gt;<br /> &lt;div class=&quot;&quot; style=&quot;margin-top: 10px;&quot;&gt;<br /> <br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Timer-01.png | 30px | alt=Send Timer]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Send Timer'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Escalation (Start)-01.png | 30px| alt=Escalation (start) ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Escalation (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Escalation (End)-01.png | 30px| alt=Escalation (end) ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Escalation (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Link (Standard)-01.png | 30px | alt=Link (start)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Link (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Link (End)-01.png | 30px | alt='Link (end)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Link (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Error (Start)-01.png | 30px | alt=Error (start)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Error (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Error (End)-01.png | 30px| alt=Error (end)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Error (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Cancel (Standard)-01.png | 30px | alt=Cancel (start)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Cancel (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Cancel (End)-01.png | 30px | alt=Cancel (end)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Cancel (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Conditional-01.png | 30px | alt=Conditional]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Conditional'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Compensation (Start)-01.png | 30px | alt=Compensation (start)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Compensation (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Compensation (End)-01.png | 30px | alt=Compensation (end)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Compensation (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Signal (Standard)-01.png | 30px | alt=Signal (start)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Signal (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Signal (End)-01.png | 30px | alt=Signal (end)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Signal (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Multiple (Standard)-01.png | 30px | alt=Multiple (start)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Multiple (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Multiple (End)-01.png | 30px | alt=Multiple (end)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Multiple (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Parallel Multiple-01.png | 30px| alt=Parallel Multiple ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Parallel Multiple'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Terminate-01.png | 30px| alt=Terminate ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Terminate'''&lt;/span&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> <br /> &lt;/div&gt;<br /> &lt;div class=&quot;row&quot; style=&quot;margin-top: 10px; margin-bottom: 50px;&quot;&gt;<br /> &lt;div class=&quot;col-md-3 nopadding&quot;&gt;<br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''GATEWAYS'''<br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;media-notations&quot; style=&quot;margin-top: 10px;&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Gateway-01.png | 30px | alt=Gateway]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Event-based Gateway-01.png | 30px | alt=Event-based Gateway]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Event-based Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Inclusive Gateway-01.png | 30px | alt=Inclusive Gateway]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Inclusive Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Exclusive Gateway-01.png | 30px | alt=Exclusive Gateway]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Exclusive Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Exclusive Event-based Gateway-01.png | 30px | alt=Exclusive Event-based Gateway]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Exclusive Event-based Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Parallel Gateway-01.png | 30px | alt=Parallel Gateway]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Parallel Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Parallel Event-based Gateway-01.png | 30px| alt=Parallel Event-based Gateway ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Parallel Event-based Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Complex Gateway-01.png | 30px| alt=Complex Gateway ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Complex Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div class=&quot;col-md-3&quot;&gt;<br /> <br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''CONVERSATIONS'''<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot; style=&quot;margin-top: 10px;&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Multiple (Standard)-01.png | 30px ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''A Conversation'''&lt;/span&gt;<br /> :defines a set of logically related message exchanges. When market with a '''(+)''' symbol it indicates a Sub-Conversation, a compound conversation element.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Multiple (Standard)-01.png | 30px | alt=A Call Conversation]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''A Call Conversation'''&lt;/span&gt;<br /> :is a wrapper for a globally defined Conversation of Sub-Conversation. A call to a Sub-Conversation is market with a '''(+)''' symbol.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Link-01.png | 30px | alt=A Conversation Link]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''A Conversation Link'''&lt;/span&gt;<br /> :connects Conversations And Participants.<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> [[ Image:XPMN.png |1500px]]<br /> [[Category:Objects]]<br /> {{DISPLAYTITLE:X-BPMN Notations}}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:Timer-01.png&diff=1322 2015-08-31T13:20:58Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:Sub-process_Marker-01.png&diff=1321 2015-08-31T13:19:34Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:Script_Task-01.png&diff=1320 2015-08-31T13:18:07Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:Escalation_(Start)-01.png&diff=1319 2015-08-31T13:16:58Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:Escalation_(End)-01.png&diff=1318 2015-08-31T13:15:39Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:Error_(Start)-01.png&diff=1317 2015-08-31T13:14:06Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:Error_(End)-01.png&diff=1316 2015-08-31T13:13:23Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:Default_Flow-01.png&diff=1315 2015-08-31T11:09:48Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=Objects:X-BPMN_Notations&diff=1314 2015-08-31T11:08:11Z

<p>Fbajohr: </p> <hr /> <div>&lt;div class=&quot;row&quot;&gt;<br /> <br /> &lt;div class=&quot;col-md-3 nopadding&quot;&gt; <br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''TASK TYPES'''<br /> &lt;/div&gt;<br /> &lt;div class=&quot;no-left-padding&quot; style=&quot;margin-top: 10px;&quot;&gt;<br /> <br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Send-01.png | 30px | alt=Send]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Send Task'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Receive-01.png | 30px | alt=Receive]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Receive Task'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:User Task-01.png | 30px | alt=User]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''User Task'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Manual Task-01.png | 30px | alt=Task]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Manual Task'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Service-01.png | 30px | alt=Service]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Manual Service Task'''&lt;/span&gt;<br /> :A Manual Service is when the service is performed by a human.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Automated Service-01.png | 30px | alt=Service]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Automated Service Task'''&lt;/span&gt;<br /> :An Automated Service can be either an application service, data service, platform service, infrastructure service or a web service.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Automated Task-01.png | 30px | alt=Activity]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Automated Task'''&lt;/span&gt;<br /> :An Automated Task is an activity that is automated through either a business process execution engine or any application (e.g. using application features and/or functions to enable the application task).<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Business Rule Task-01.png | 30px | alt=Rule]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Business Rule Task'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Reporting-01.png | 30px| alt=Reporting ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Reporting Task'''&lt;/span&gt;<br /> :Reporting is the exposure, description and portrayment of specific tasks, services and the associated information and data.The information and data objects/source can bind with the reporting activity the process components to the specific cockpits,dashboards or scorecards.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Mapping-01.png | 30px | alt=Mapping]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Mapping Task'''&lt;/span&gt;<br /> :Mapping activities includes identifying, defining and plotting the involved business, information and data objects within theactivities. This allows to identify possible grouping of common business, information and data objects and their associatedrules (e.g. rulesets), enabling the change of complex objects and views into more simple views.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Decision Table-01.png | 30px| alt=Table ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Decision Table'''&lt;/span&gt;<br /> :A Decision Table defines decisions based on a number of given conditions and actions. Decision tables allow to work from the same information, and are therefore a precise way to model complicated logics and associations.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Notification-01.png | 30px | alt=Notification]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Notification Task'''&lt;/span&gt;<br /> :An instance of a message delivered to one or more recipients. A Notification activity sends a message to a user, both therecipients and the content that needs to be specified. Notification activities furthermore allow flow rulesets to be applied inorder to notify users of events that occur during the workflow.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Script-01.png | 30px | alt=Script]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Script Task'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Rule-01.png | 30px | alt=Rule]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Rule'''&lt;/span&gt;<br /> :A Rule is a statement describing a business policy or decision procedure. Some programming languages run business rules together in very complex algorithms. In business process analysis, each rule is usually stated independently, in the general format of: If A and B, Then C.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - RuleScript-01.png | 30px | alt=RuleScript]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Rule Script'''&lt;/span&gt;<br /> :A Rule Script allows generating a rule in a scripting environment. This is done through the connection of other activities andthe rules that govern these relations, and the actions between them. Rule scripts can furthermore be used with script types,and thereby automated test rules (e.g. configurable, programmed, query and event-based network alerts). The link betweenrule scripts and the mentioned script type could be used as template–based query that can be run against backend tables ordatabase views.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - RuleSet-01.png | 30px | alt=RuleSet]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Ruleset'''&lt;/span&gt;<br /> :A Ruleset is a collection (and thereby a grouping) of rules. They are either grouped based on common related rules, decisions tables or the need to govern a specific set or behavior of tasks. Grouping such rulesets allows for sharing of rules and execution by a rules engine.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Rule Flow-01.png | 30px | alt=Rule Flow]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Rule Flow'''&lt;/span&gt;<br /> :Rule Flows are comprised of linked tasks that contain the instructions for which rules to execute and in what order. The rulesare organized into tasks, and the rule flow specifies how tasks are chained together; how, when, and under what conditionsthey are executed. When you are dealing with many large rulesets, managing the order in which rules are evaluated canbecome complex. Rule flows allows you to specify the order in which rulesets are to be evaluated. It does so by providing youwith a flow chart. Use this chart to define which rule sets should be evaluated in sequence, and which ones in parallel, and tospecify conditions under which rule sets should be evaluated. The reuse of rules components and their natural relations likeactivity association are an important aspect of rule modelling principles. This allows for rule modelling consistency betweenthe different rule artifacts from the rule flows, rule scripts, rulesets, flow rulesets, rules and decision tables.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Flow Ruleset-01.png | 30px | alt=Flow Ruleset]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Flow Ruleset'''&lt;/span&gt;<br /> :A Flow Ruleset is a collection (and thereby grouping) of rules that apply to a flow. These flow rulesets are either grouped based on common related rules in the flow, decisions tables, or the need to govern a specific set or behavior of tasks in the flow. Grouping such flow rulesets allows for sharing of rules and execution, by a rule engine throughout the entire flow. As well as the relation to the reuse of such rulsets in other flows, starting from the main flow where the ruleset are applied.<br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;col-md-3&quot;&gt; <br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''MARKERS'''<br /> &lt;/div&gt;<br /> &lt;div class=&quot;&quot; style=&quot;margin-top: 10px;&quot;&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Sub-process-01.png | 30px | alt=Sub-process Marker]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Sub-process Marker'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Loop-01.png | 30px | alt=Loop Marker]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Loop Marker'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Parallel Multiple Instance-01.png | 30px | alt=Parallel MI Marker]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Parallel MI Marker'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Sequential Multiple Instance-01.png | 30px | alt=Sequential MI Marker]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Sequential MI Marker'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image: Ad Hoc Marker-01.png | 30px | alt='Ad Hoc Marker]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Ad Hoc Marker'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Compensation-01.png | 30px| alt=Compensation ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Compensation'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;&lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Annotation-01.png | 30px | alt=Annotation Marker']]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Annotation Marker'''&lt;/span&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;&quot; style=&quot;margin-top: 10px;&quot;&gt;<br /> <br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''FLOWS'''<br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;media-notations&quot; style=&quot;margin-top:10px;&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Link-01.png | 30px | alt=Sequence Flow]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Sequence Flow'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot; style=&quot;margin-top:10px;&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Conditional Flow-01.png | 30px | alt=Conditional flow]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''ConditionalFlow'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Link-01.png | 30px | alt=Message Flow]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Message Flow'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Link-01.png | 30px | alt=Association Flow]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Association Flow'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Link-01.png | 30px | alt=Data Association Flow]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Data Association Flow'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> <br /> <br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;col-md-3 nopadding&quot;&gt; <br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''OBJECTS'''<br /> &lt;/div&gt;<br /> &lt;div class=&quot;no-left-padding&quot; style=&quot;margin-top: 10px;&quot;&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Business Object-01.png | 30px | alt=Business Object]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Business Object'''&lt;/span&gt;<br /> :A Business Object is the term used to express real-world objects like people, employee, products or a sales order, customerand revenue. Business Objects used for example in business, process and service mapping and furthermore used in applicationimplementations where they are used as a patented semantic layer that shields users from the complexities of informationtable names and data relationships.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Business Store-01.png | 30px | alt=Business Store]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Business Store'''&lt;/span&gt;<br /> :Is a place where the real-world objects are stored.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Business Input-01.png | 30px | alt=Business Input]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Business Input'''&lt;/span&gt;<br /> :Is an external input for the real-world objects. A kind of input parameter.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Business Output-01.png | 30px| alt=Business Output ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Business Output'''&lt;/span&gt;<br /> :Is the real-world result of the entire process and or service flow. A kind of output parameter.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Collection of Business Objects-01.png | 30px | alt=Collection of Business Objects]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Collection of Business Objects'''&lt;/span&gt;<br /> :Represents a collection of real-world objects, e.g. a employee roles.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Information Object-01.png | 30px | alt=Information Objects]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Information Objects'''&lt;/span&gt;<br /> :An Information Object is used to specify information about real-world objects (like people, employees, products or a salesorder, etc.), and is therefore a digital representation of an existing entity within an Information System (e.g. Oracle ERP or SAPERP). It encompasses both the business information (in the form of functions and methods) and the application information(in the form of attributes) of the entity. Information Objects can be found and therefore modeled in business functions,business services and business processes.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Information Input-01.png | 30px | alt=Information Input]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Information Input'''&lt;/span&gt;<br /> :Is an external information input for the entire process. A kind of input parameter.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Information Output-01.png | 30px ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Information Output'''&lt;/span&gt;<br /> :Is the information output/result of the entire process. A kind of output parameter.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Information Store-01.png | 30px | alt=Information Store]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Information Store'''&lt;/span&gt;<br /> :Is a place where the information can be read or written (e.g. knowledge management or a filingcabinet). It persists beyond the lifetime of the process instance.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Collection of Information Objects-01.png | 30px | alt=Collection of Information Objects]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Collection of Information Objects'''&lt;/span&gt;<br /> :Represents a collection of information (e.g. a list of order items).<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Data Objects - Data Object-01.png | 30px | alt=Data Object]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Data Object'''&lt;/span&gt;<br /> :A Data Object is a logical cluster of all tables in the data set that have one or more columns containing data related to the same business entity. Data objects are not maps, but instead represent an object view of related Information Objects and they represent Business Objects.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Data Objects - Data Input-01.png | 30px | alt=Data Input]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Data Input'''&lt;/span&gt;<br /> :Is an external data input for the entire process. A kind of input parameter.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Data Objects - Data Output-01.png | 30px | alt=Data Output]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Data Output'''&lt;/span&gt;<br /> :Is the data result of the entire process. A kind of output parameter.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Data Objects - Data Store-01.png | 30px | alt=Data Store]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Data Store'''&lt;/span&gt;<br /> :Is a place where the process can read or write data (e.g. a database or a filing cabinet). It persists beyond the lifetime of the process instance.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Data Objects - Collection of Data Objects-01.png | 30px | alt=Collection of Data Objects]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Collection of Data Objects'''&lt;/span&gt;<br /> :Represents a collection of data tables/columns containing data related to the same data entity (e.g. a list of order items).<br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> <br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;col-md-3&quot;&gt; <br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''EVENTS'''<br /> &lt;/div&gt;<br /> &lt;div class=&quot;&quot; style=&quot;margin-top: 10px;&quot;&gt;<br /> <br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Timer-01.png | 30px | alt=Send Timer]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Send Timer'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Escalation (Standard)-01.png | 30px| alt=Escalation (start) ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Escalation (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Escalation (End)-01.png | 30px| alt=Escalation (end) ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Escalation (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Link (Standard)-01.png | 30px | alt=Link (start)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Link (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Link (End)-01.png | 30px | alt='Link (end)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Link (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Error (Standard)-01.png | 30px | alt=Error (start)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Error (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Error (End)-01.png | 30px| alt=Error (end)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Error (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Cancel (Standard)-01.png | 30px | alt=Cancel (start)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Cancel (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Cancel (End)-01.png | 30px | alt=Cancel (end)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Cancel (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Conditional-01.png | 30px | alt=Conditional]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Conditional'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Compensation (Start)-01.png | 30px | alt=Compensation (start)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Compensation (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Compensation (End)-01.png | 30px | alt=Compensation (end)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Compensation (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Signal (Standard)-01.png | 30px | alt=Signal (start)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Signal (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Signal (End)-01.png | 30px | alt=Signal (end)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Signal (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Multiple (Standard)-01.png | 30px | alt=Multiple (start)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Multiple (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Multiple (End)-01.png | 30px | alt=Multiple (end)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Multiple (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Parallel Multiple-01.png | 30px| alt=Parallel Multiple ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Parallel Multiple'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Terminate-01.png | 30px| alt=Terminate ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Terminate'''&lt;/span&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> <br /> &lt;/div&gt;<br /> &lt;div class=&quot;row&quot; style=&quot;margin-top: 10px; margin-bottom: 50px;&quot;&gt;<br /> &lt;div class=&quot;col-md-3 nopadding&quot;&gt;<br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''GATEWAYS'''<br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;media-notations&quot; style=&quot;margin-top: 10px;&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Gateway-01.png | 30px | alt=Gateway]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Event-based Gateway-01.png | 30px | alt=Event-based Gateway]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Event-based Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Inclusive Gateway-01.png | 30px | alt=Inclusive Gateway]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Inclusive Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Exclusive Gateway-01.png | 30px | alt=Exclusive Gateway]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Exclusive Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Exclusive Event-based Gateway-01.png | 30px | alt=Exclusive Event-based Gateway]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Exclusive Event-based Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Parallel Gateway-01.png | 30px | alt=Parallel Gateway]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Parallel Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Parallel Event-based Gateway-01.png | 30px| alt=Parallel Event-based Gateway ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Parallel Event-based Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Complex Gateway-01.png | 30px| alt=Complex Gateway ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Complex Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div class=&quot;col-md-3&quot;&gt;<br /> <br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''CONVERSATIONS'''<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot; style=&quot;margin-top: 10px;&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Multiple (Standard)-01.png | 30px ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''A Conversation'''&lt;/span&gt;<br /> :defines a set of logically related message exchanges. When market with a '''(+)''' symbol it indicates a Sub-Conversation, a compound conversation element.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Multiple (Standard)-01.png | 30px | alt=A Call Conversation]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''A Call Conversation'''&lt;/span&gt;<br /> :is a wrapper for a globally defined Conversation of Sub-Conversation. A call to a Sub-Conversation is market with a '''(+)''' symbol.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Link-01.png | 30px | alt=A Conversation Link]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''A Conversation Link'''&lt;/span&gt;<br /> :connects Conversations And Participants.<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> [[ Image:XPMN.png |1500px]]<br /> [[Category:Objects]]<br /> {{DISPLAYTITLE:X-BPMN Notations}}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=Objects:X-BPMN_Notations&diff=1313 2015-08-31T11:05:01Z

<p>Fbajohr: </p> <hr /> <div>&lt;div class=&quot;row&quot;&gt;<br /> <br /> &lt;div class=&quot;col-md-3 nopadding&quot;&gt; <br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''TASK TYPES'''<br /> &lt;/div&gt;<br /> &lt;div class=&quot;no-left-padding&quot; style=&quot;margin-top: 10px;&quot;&gt;<br /> <br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Send-01.png | 30px | alt=Send]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Send Task'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Receive-01.png | 30px | alt=Receive]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Receive Task'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:User Task-01.png | 30px | alt=User]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''User Task'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Manual Task-01.png | 30px | alt=Task]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Manual Task'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Service-01.png | 30px | alt=Service]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Manual Service Task'''&lt;/span&gt;<br /> :A Manual Service is when the service is performed by a human.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Automated Service-01.png | 30px | alt=Service]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Automated Service Task'''&lt;/span&gt;<br /> :An Automated Service can be either an application service, data service, platform service, infrastructure service or a web service.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Automated Task-01.png | 30px | alt=Activity]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Automated Task'''&lt;/span&gt;<br /> :An Automated Task is an activity that is automated through either a business process execution engine or any application (e.g. using application features and/or functions to enable the application task).<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Business Rule Task-01.png | 30px | alt=Rule]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Business Rule Task'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Reporting-01.png | 30px| alt=Reporting ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Reporting Task'''&lt;/span&gt;<br /> :Reporting is the exposure, description and portrayment of specific tasks, services and the associated information and data.The information and data objects/source can bind with the reporting activity the process components to the specific cockpits,dashboards or scorecards.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Mapping-01.png | 30px | alt=Mapping]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Mapping Task'''&lt;/span&gt;<br /> :Mapping activities includes identifying, defining and plotting the involved business, information and data objects within theactivities. This allows to identify possible grouping of common business, information and data objects and their associatedrules (e.g. rulesets), enabling the change of complex objects and views into more simple views.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Decision Table-01.png | 30px| alt=Table ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Decision Table'''&lt;/span&gt;<br /> :A Decision Table defines decisions based on a number of given conditions and actions. Decision tables allow to work from the same information, and are therefore a precise way to model complicated logics and associations.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Notification-01.png | 30px | alt=Notification]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Notification Task'''&lt;/span&gt;<br /> :An instance of a message delivered to one or more recipients. A Notification activity sends a message to a user, both therecipients and the content that needs to be specified. Notification activities furthermore allow flow rulesets to be applied inorder to notify users of events that occur during the workflow.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Script-01.png | 30px | alt=Script]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Script Task'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Rule-01.png | 30px | alt=Rule]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Rule'''&lt;/span&gt;<br /> :A Rule is a statement describing a business policy or decision procedure. Some programming languages run business rules together in very complex algorithms. In business process analysis, each rule is usually stated independently, in the general format of: If A and B, Then C.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - RuleScript-01.png | 30px | alt=RuleScript]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Rule Script'''&lt;/span&gt;<br /> :A Rule Script allows generating a rule in a scripting environment. This is done through the connection of other activities andthe rules that govern these relations, and the actions between them. Rule scripts can furthermore be used with script types,and thereby automated test rules (e.g. configurable, programmed, query and event-based network alerts). The link betweenrule scripts and the mentioned script type could be used as template–based query that can be run against backend tables ordatabase views.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - RuleSet-01.png | 30px | alt=RuleSet]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Ruleset'''&lt;/span&gt;<br /> :A Ruleset is a collection (and thereby a grouping) of rules. They are either grouped based on common related rules, decisions tables or the need to govern a specific set or behavior of tasks. Grouping such rulesets allows for sharing of rules and execution by a rules engine.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Rule Flow-01.png | 30px | alt=Rule Flow]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Rule Flow'''&lt;/span&gt;<br /> :Rule Flows are comprised of linked tasks that contain the instructions for which rules to execute and in what order. The rulesare organized into tasks, and the rule flow specifies how tasks are chained together; how, when, and under what conditionsthey are executed. When you are dealing with many large rulesets, managing the order in which rules are evaluated canbecome complex. Rule flows allows you to specify the order in which rulesets are to be evaluated. It does so by providing youwith a flow chart. Use this chart to define which rule sets should be evaluated in sequence, and which ones in parallel, and tospecify conditions under which rule sets should be evaluated. The reuse of rules components and their natural relations likeactivity association are an important aspect of rule modelling principles. This allows for rule modelling consistency betweenthe different rule artifacts from the rule flows, rule scripts, rulesets, flow rulesets, rules and decision tables.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Flow Ruleset-01.png | 30px | alt=Flow Ruleset]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Flow Ruleset'''&lt;/span&gt;<br /> :A Flow Ruleset is a collection (and thereby grouping) of rules that apply to a flow. These flow rulesets are either grouped based on common related rules in the flow, decisions tables, or the need to govern a specific set or behavior of tasks in the flow. Grouping such flow rulesets allows for sharing of rules and execution, by a rule engine throughout the entire flow. As well as the relation to the reuse of such rulsets in other flows, starting from the main flow where the ruleset are applied.<br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;col-md-3&quot;&gt; <br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''MARKERS'''<br /> &lt;/div&gt;<br /> &lt;div class=&quot;&quot; style=&quot;margin-top: 10px;&quot;&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Sub-process-01.png | 30px | alt=Sub-process Marker]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Sub-process Marker'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Loop-01.png | 30px | alt=Loop Marker]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Loop Marker'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Parallel Multiple Instance-01.png | 30px | alt=Parallel MI Marker]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Parallel MI Marker'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Sequential Multiple Instance-01.png | 30px | alt=Sequential MI Marker]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Sequential MI Marker'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image: Ad Hoc Marker-01.png | 30px | alt='Ad Hoc Marker]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Ad Hoc Marker'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Compensation-01.png | 30px| alt=Compensation ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Compensation'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;&lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Annotation-01.png | 30px | alt=Annotation Marker']]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Annotation Marker'''&lt;/span&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;&quot; style=&quot;margin-top: 10px;&quot;&gt;<br /> <br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''FLOWS'''<br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;media-notations&quot; style=&quot;margin-top:10px;&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Link-01.png | 30px | alt=Sequence Flow]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Sequence Flow'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Link-01.png | 30px | alt=Message Flow]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Message Flow'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Link-01.png | 30px | alt=Association Flow]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Association Flow'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Link-01.png | 30px | alt=Data Association Flow]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Data Association Flow'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> <br /> <br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;col-md-3 nopadding&quot;&gt; <br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''OBJECTS'''<br /> &lt;/div&gt;<br /> &lt;div class=&quot;no-left-padding&quot; style=&quot;margin-top: 10px;&quot;&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Business Object-01.png | 30px | alt=Business Object]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Business Object'''&lt;/span&gt;<br /> :A Business Object is the term used to express real-world objects like people, employee, products or a sales order, customerand revenue. Business Objects used for example in business, process and service mapping and furthermore used in applicationimplementations where they are used as a patented semantic layer that shields users from the complexities of informationtable names and data relationships.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Business Store-01.png | 30px | alt=Business Store]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Business Store'''&lt;/span&gt;<br /> :Is a place where the real-world objects are stored.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Business Input-01.png | 30px | alt=Business Input]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Business Input'''&lt;/span&gt;<br /> :Is an external input for the real-world objects. A kind of input parameter.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Business Output-01.png | 30px| alt=Business Output ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Business Output'''&lt;/span&gt;<br /> :Is the real-world result of the entire process and or service flow. A kind of output parameter.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Collection of Business Objects-01.png | 30px | alt=Collection of Business Objects]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Collection of Business Objects'''&lt;/span&gt;<br /> :Represents a collection of real-world objects, e.g. a employee roles.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Information Object-01.png | 30px | alt=Information Objects]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Information Objects'''&lt;/span&gt;<br /> :An Information Object is used to specify information about real-world objects (like people, employees, products or a salesorder, etc.), and is therefore a digital representation of an existing entity within an Information System (e.g. Oracle ERP or SAPERP). It encompasses both the business information (in the form of functions and methods) and the application information(in the form of attributes) of the entity. Information Objects can be found and therefore modeled in business functions,business services and business processes.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Information Input-01.png | 30px | alt=Information Input]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Information Input'''&lt;/span&gt;<br /> :Is an external information input for the entire process. A kind of input parameter.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Information Output-01.png | 30px ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Information Output'''&lt;/span&gt;<br /> :Is the information output/result of the entire process. A kind of output parameter.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Information Store-01.png | 30px | alt=Information Store]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Information Store'''&lt;/span&gt;<br /> :Is a place where the information can be read or written (e.g. knowledge management or a filingcabinet). It persists beyond the lifetime of the process instance.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Collection of Information Objects-01.png | 30px | alt=Collection of Information Objects]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Collection of Information Objects'''&lt;/span&gt;<br /> :Represents a collection of information (e.g. a list of order items).<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Data Objects - Data Object-01.png | 30px | alt=Data Object]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Data Object'''&lt;/span&gt;<br /> :A Data Object is a logical cluster of all tables in the data set that have one or more columns containing data related to the same business entity. Data objects are not maps, but instead represent an object view of related Information Objects and they represent Business Objects.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Data Objects - Data Input-01.png | 30px | alt=Data Input]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Data Input'''&lt;/span&gt;<br /> :Is an external data input for the entire process. A kind of input parameter.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Data Objects - Data Output-01.png | 30px | alt=Data Output]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Data Output'''&lt;/span&gt;<br /> :Is the data result of the entire process. A kind of output parameter.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Data Objects - Data Store-01.png | 30px | alt=Data Store]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Data Store'''&lt;/span&gt;<br /> :Is a place where the process can read or write data (e.g. a database or a filing cabinet). It persists beyond the lifetime of the process instance.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Data Objects - Collection of Data Objects-01.png | 30px | alt=Collection of Data Objects]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Collection of Data Objects'''&lt;/span&gt;<br /> :Represents a collection of data tables/columns containing data related to the same data entity (e.g. a list of order items).<br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> <br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;col-md-3&quot;&gt; <br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''EVENTS'''<br /> &lt;/div&gt;<br /> &lt;div class=&quot;&quot; style=&quot;margin-top: 10px;&quot;&gt;<br /> <br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Timer-01.png | 30px | alt=Send Timer]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Send Timer'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Escalation (Standard)-01.png | 30px| alt=Escalation (start) ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Escalation (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Escalation (End)-01.png | 30px| alt=Escalation (end) ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Escalation (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Link (Standard)-01.png | 30px | alt=Link (start)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Link (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Link (End)-01.png | 30px | alt='Link (end)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Link (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Error (Standard)-01.png | 30px | alt=Error (start)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Error (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Error (End)-01.png | 30px| alt=Error (end)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Error (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Cancel (Standard)-01.png | 30px | alt=Cancel (start)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Cancel (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Cancel (End)-01.png | 30px | alt=Cancel (end)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Cancel (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Conditional-01.png | 30px | alt=Conditional]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Conditional'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Compensation (Start)-01.png | 30px | alt=Compensation (start)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Compensation (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Compensation (End)-01.png | 30px | alt=Compensation (end)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Compensation (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Signal (Standard)-01.png | 30px | alt=Signal (start)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Signal (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Signal (End)-01.png | 30px | alt=Signal (end)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Signal (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Multiple (Standard)-01.png | 30px | alt=Multiple (start)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Multiple (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Multiple (End)-01.png | 30px | alt=Multiple (end)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Multiple (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Parallel Multiple-01.png | 30px| alt=Parallel Multiple ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Parallel Multiple'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Terminate-01.png | 30px| alt=Terminate ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Terminate'''&lt;/span&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> <br /> &lt;/div&gt;<br /> &lt;div class=&quot;row&quot; style=&quot;margin-top: 10px; margin-bottom: 50px;&quot;&gt;<br /> &lt;div class=&quot;col-md-3 nopadding&quot;&gt;<br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''GATEWAYS'''<br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;media-notations&quot; style=&quot;margin-top: 10px;&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Gateway-01.png | 30px | alt=Gateway]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Event-based Gateway-01.png | 30px | alt=Event-based Gateway]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Event-based Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Inclusive Gateway-01.png | 30px | alt=Inclusive Gateway]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Inclusive Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Exclusive Gateway-01.png | 30px | alt=Exclusive Gateway]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Exclusive Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Exclusive Event-based Gateway-01.png | 30px | alt=Exclusive Event-based Gateway]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Exclusive Event-based Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Parallel Gateway-01.png | 30px | alt=Parallel Gateway]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Parallel Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Parallel Event-based Gateway-01.png | 30px| alt=Parallel Event-based Gateway ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Parallel Event-based Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Complex Gateway-01.png | 30px| alt=Complex Gateway ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Complex Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div class=&quot;col-md-3&quot;&gt;<br /> <br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''CONVERSATIONS'''<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot; style=&quot;margin-top: 10px;&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Multiple (Standard)-01.png | 30px ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''A Conversation'''&lt;/span&gt;<br /> :defines a set of logically related message exchanges. When market with a '''(+)''' symbol it indicates a Sub-Conversation, a compound conversation element.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Multiple (Standard)-01.png | 30px | alt=A Call Conversation]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''A Call Conversation'''&lt;/span&gt;<br /> :is a wrapper for a globally defined Conversation of Sub-Conversation. A call to a Sub-Conversation is market with a '''(+)''' symbol.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Link-01.png | 30px | alt=A Conversation Link]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''A Conversation Link'''&lt;/span&gt;<br /> :connects Conversations And Participants.<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> [[ Image:XPMN.png |1500px]]<br /> [[Category:Objects]]<br /> {{DISPLAYTITLE:X-BPMN Notations}}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:Conditional_Flow-01.png&diff=1312 2015-08-31T10:46:45Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:Compensation_(Start)-01.png&diff=1311 2015-08-31T10:45:12Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:Compensation_(End)-01.png&diff=1310 2015-08-31T10:44:03Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:Call_Activity-01.png&diff=1309 2015-08-31T10:39:21Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:Business_Rule_Task-01.png&diff=1308 2015-08-31T10:35:06Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=Objects:X-BPMN_Notations&diff=1257 2015-08-28T13:05:16Z

<p>Fbajohr: </p> <hr /> <div>&lt;div class=&quot;row&quot;&gt;<br /> <br /> &lt;div class=&quot;col-md-3 nopadding&quot;&gt; <br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''TASK TYPES'''<br /> &lt;/div&gt;<br /> &lt;div class=&quot;no-left-padding&quot; style=&quot;margin-top: 10px;&quot;&gt;<br /> <br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Send-01.png | 30px | alt=Send]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Send Task'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Receive-01.png | 30px | alt=Receive]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Receive Task'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:User Task-01.png | 30px | alt=User]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''User Task'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Manual Task-01.png | 30px | alt=Task]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Manual Task'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Service-01.png | 30px | alt=Service]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Manual Service Task'''&lt;/span&gt;<br /> :A Manual Service is when the service is performed by a human.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Automated Service-01.png | 30px | alt=Service]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Automated Service Task'''&lt;/span&gt;<br /> :An Automated Service can be either an application service, data service, platform service, infrastructure service or a web service.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Automated Task-01.png | 30px | alt=Activity]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Automated Task'''&lt;/span&gt;<br /> :An Automated Task is an activity that is automated through either a business process execution engine or any application (e.g. using application features and/or functions to enable the application task).<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Business Rule-01.png | 30px | alt=Rule]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Rule Task'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Reporting-01.png | 30px| alt=Reporting ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Reporting Task'''&lt;/span&gt;<br /> :Reporting is the exposure, description and portrayment of specific tasks, services and the associated information and data.The information and data objects/source can bind with the reporting activity the process components to the specific cockpits,dashboards or scorecards.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Mapping-01.png | 30px | alt=Mapping]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Mapping Task'''&lt;/span&gt;<br /> :Mapping activities includes identifying, defining and plotting the involved business, information and data objects within theactivities. This allows to identify possible grouping of common business, information and data objects and their associatedrules (e.g. rulesets), enabling the change of complex objects and views into more simple views.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Decision Table-01.png | 30px| alt=Table ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Decision Table'''&lt;/span&gt;<br /> :A Decision Table defines decisions based on a number of given conditions and actions. Decision tables allow to work from the same information, and are therefore a precise way to model complicated logics and associations.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Notification-01.png | 30px | alt=Notification]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Notification Task'''&lt;/span&gt;<br /> :An instance of a message delivered to one or more recipients. A Notification activity sends a message to a user, both therecipients and the content that needs to be specified. Notification activities furthermore allow flow rulesets to be applied inorder to notify users of events that occur during the workflow.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Script-01.png | 30px | alt=Script]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Script Task'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Rule-01.png | 30px | alt=Rule]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Rule'''&lt;/span&gt;<br /> :A Rule is a statement describing a business policy or decision procedure. Some programming languages run business rules together in very complex algorithms. In business process analysis, each rule is usually stated independently, in the general format of: If A and B, Then C.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - RuleScript-01.png | 30px | alt=RuleScript]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Rule Script'''&lt;/span&gt;<br /> :A Rule Script allows generating a rule in a scripting environment. This is done through the connection of other activities andthe rules that govern these relations, and the actions between them. Rule scripts can furthermore be used with script types,and thereby automated test rules (e.g. configurable, programmed, query and event-based network alerts). The link betweenrule scripts and the mentioned script type could be used as template–based query that can be run against backend tables ordatabase views.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - RuleSet-01.png | 30px | alt=RuleSet]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Ruleset'''&lt;/span&gt;<br /> :A Ruleset is a collection (and thereby a grouping) of rules. They are either grouped based on common related rules, decisions tables or the need to govern a specific set or behavior of tasks. Grouping such rulesets allows for sharing of rules and execution by a rules engine.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Rule Flow-01.png | 30px | alt=Rule Flow]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Rule Flow'''&lt;/span&gt;<br /> :Rule Flows are comprised of linked tasks that contain the instructions for which rules to execute and in what order. The rulesare organized into tasks, and the rule flow specifies how tasks are chained together; how, when, and under what conditionsthey are executed. When you are dealing with many large rulesets, managing the order in which rules are evaluated canbecome complex. Rule flows allows you to specify the order in which rulesets are to be evaluated. It does so by providing youwith a flow chart. Use this chart to define which rule sets should be evaluated in sequence, and which ones in parallel, and tospecify conditions under which rule sets should be evaluated. The reuse of rules components and their natural relations likeactivity association are an important aspect of rule modelling principles. This allows for rule modelling consistency betweenthe different rule artifacts from the rule flows, rule scripts, rulesets, flow rulesets, rules and decision tables.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Flow Ruleset-01.png | 30px | alt=Flow Ruleset]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Flow Ruleset'''&lt;/span&gt;<br /> :A Flow Ruleset is a collection (and thereby grouping) of rules that apply to a flow. These flow rulesets are either grouped based on common related rules in the flow, decisions tables, or the need to govern a specific set or behavior of tasks in the flow. Grouping such flow rulesets allows for sharing of rules and execution, by a rule engine throughout the entire flow. As well as the relation to the reuse of such rulsets in other flows, starting from the main flow where the ruleset are applied.<br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;col-md-3&quot;&gt; <br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''MARKERS'''<br /> &lt;/div&gt;<br /> &lt;div class=&quot;&quot; style=&quot;margin-top: 10px;&quot;&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Sub-process-01.png | 30px | alt=Sub-process Marker]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Sub-process Marker'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Loop-01.png | 30px | alt=Loop Marker]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Loop Marker'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Parallel Multiple Instance-01.png | 30px | alt=Parallel MI Marker]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Parallel MI Marker'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Sequential Multiple Instance-01.png | 30px | alt=Sequential MI Marker]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Sequential MI Marker'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image: Ad Hoc Marker-01.png | 30px | alt='Ad Hoc Marker]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Ad Hoc Marker'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Compensation-01.png | 30px| alt=Compensation ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Compensation'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;&lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Annotation-01.png | 30px | alt=Annotation Marker']]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Annotation Marker'''&lt;/span&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;&quot; style=&quot;margin-top: 10px;&quot;&gt;<br /> <br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''FLOWS'''<br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;media-notations&quot; style=&quot;margin-top:10px;&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Link-01.png | 30px | alt=Sequence Flow]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Sequence Flow'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Link-01.png | 30px | alt=Message Flow]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Message Flow'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Link-01.png | 30px | alt=Association Flow]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Association Flow'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Link-01.png | 30px | alt=Data Association Flow]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Data Association Flow'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> <br /> <br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;col-md-3 nopadding&quot;&gt; <br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''OBJECTS'''<br /> &lt;/div&gt;<br /> &lt;div class=&quot;no-left-padding&quot; style=&quot;margin-top: 10px;&quot;&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Business Object-01.png | 30px | alt=Business Object]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Business Object'''&lt;/span&gt;<br /> :A Business Object is the term used to express real-world objects like people, employee, products or a sales order, customerand revenue. Business Objects used for example in business, process and service mapping and furthermore used in applicationimplementations where they are used as a patented semantic layer that shields users from the complexities of informationtable names and data relationships.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Business Store-01.png | 30px | alt=Business Store]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Business Store'''&lt;/span&gt;<br /> :Is a place where the real-world objects are stored.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Business Input-01.png | 30px | alt=Business Input]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Business Input'''&lt;/span&gt;<br /> :Is an external input for the real-world objects. A kind of input parameter.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Business Output-01.png | 30px| alt=Business Output ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Business Output'''&lt;/span&gt;<br /> :Is the real-world result of the entire process and or service flow. A kind of output parameter.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Collection of Business Objects-01.png | 30px | alt=Collection of Business Objects]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Collection of Business Objects'''&lt;/span&gt;<br /> :Represents a collection of real-world objects, e.g. a employee roles.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Information Object-01.png | 30px | alt=Information Objects]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Information Objects'''&lt;/span&gt;<br /> :An Information Object is used to specify information about real-world objects (like people, employees, products or a salesorder, etc.), and is therefore a digital representation of an existing entity within an Information System (e.g. Oracle ERP or SAPERP). It encompasses both the business information (in the form of functions and methods) and the application information(in the form of attributes) of the entity. Information Objects can be found and therefore modeled in business functions,business services and business processes.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Information Input-01.png | 30px | alt=Information Input]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Information Input'''&lt;/span&gt;<br /> :Is an external information input for the entire process. A kind of input parameter.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Information Output-01.png | 30px ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Information Output'''&lt;/span&gt;<br /> :Is the information output/result of the entire process. A kind of output parameter.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Information Store-01.png | 30px | alt=Information Store]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Information Store'''&lt;/span&gt;<br /> :Is a place where the information can be read or written (e.g. knowledge management or a filingcabinet). It persists beyond the lifetime of the process instance.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD Process Reference Framework - BPMN 2.0 - Visio Stencils - Collection of Information Objects-01.png | 30px | alt=Collection of Information Objects]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Collection of Information Objects'''&lt;/span&gt;<br /> :Represents a collection of information (e.g. a list of order items).<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Data Objects - Data Object-01.png | 30px | alt=Data Object]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Data Object'''&lt;/span&gt;<br /> :A Data Object is a logical cluster of all tables in the data set that have one or more columns containing data related to the same business entity. Data objects are not maps, but instead represent an object view of related Information Objects and they represent Business Objects.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Data Objects - Data Input-01.png | 30px | alt=Data Input]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Data Input'''&lt;/span&gt;<br /> :Is an external data input for the entire process. A kind of input parameter.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Data Objects - Data Output-01.png | 30px | alt=Data Output]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Data Output'''&lt;/span&gt;<br /> :Is the data result of the entire process. A kind of output parameter.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Data Objects - Data Store-01.png | 30px | alt=Data Store]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Data Store'''&lt;/span&gt;<br /> :Is a place where the process can read or write data (e.g. a database or a filing cabinet). It persists beyond the lifetime of the process instance.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Data Objects - Collection of Data Objects-01.png | 30px | alt=Collection of Data Objects]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Collection of Data Objects'''&lt;/span&gt;<br /> :Represents a collection of data tables/columns containing data related to the same data entity (e.g. a list of order items).<br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> <br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;col-md-3&quot;&gt; <br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''EVENTS'''<br /> &lt;/div&gt;<br /> &lt;div class=&quot;&quot; style=&quot;margin-top: 10px;&quot;&gt;<br /> <br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Timer-01.png | 30px | alt=Send Timer]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Send Timer'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Escalation (Standard)-01.png | 30px| alt=Escalation (start) ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Escalation (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Escalation (End)-01.png | 30px| alt=Escalation (end) ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Escalation (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Link (Standard)-01.png | 30px | alt=Link (start)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Link (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Link (End)-01.png | 30px | alt='Link (end)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Link (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Error (Standard)-01.png | 30px | alt=Error (start)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Error (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Error (End)-01.png | 30px| alt=Error (end)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Error (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Cancel (Standard)-01.png | 30px | alt=Cancel (start)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Cancel (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Cancel (End)-01.png | 30px | alt=Cancel (end)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Cancel (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Conditional-01.png | 30px | alt=Conditional]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Conditional'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Activity Markers - Compensation-01.png | 30px | alt=Compensation (start)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Compensation (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Compensation (End)-01.png | 30px | alt=Compensation (end)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Compensation (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Signal (Standard)-01.png | 30px | alt=Signal (start)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Signal (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Signal (End)-01.png | 30px | alt=Signal (end)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Signal (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Multiple (Standard)-01.png | 30px | alt=Multiple (start)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Multiple (start)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Multiple (End)-01.png | 30px | alt=Multiple (end)]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Multiple (end)'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Parallel Multiple-01.png | 30px| alt=Parallel Multiple ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Parallel Multiple'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Terminate-01.png | 30px| alt=Terminate ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Terminate'''&lt;/span&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> <br /> <br /> &lt;/div&gt;<br /> &lt;div class=&quot;row&quot; style=&quot;margin-top: 10px; margin-bottom: 50px;&quot;&gt;<br /> &lt;div class=&quot;col-md-3 nopadding&quot;&gt;<br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''GATEWAYS'''<br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;media-notations&quot; style=&quot;margin-top: 10px;&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Gateway-01.png | 30px | alt=Gateway]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Event-based Gateway-01.png | 30px | alt=Event-based Gateway]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Event-based Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Inclusive Gateway-01.png | 30px | alt=Inclusive Gateway]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Inclusive Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Exclusive Gateway-01.png | 30px | alt=Exclusive Gateway]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Exclusive Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Exclusive Event-based Gateway-01.png | 30px | alt=Exclusive Event-based Gateway]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Exclusive Event-based Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Parallel Gateway-01.png | 30px | alt=Parallel Gateway]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Parallel Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Parallel Event-based Gateway-01.png | 30px| alt=Parallel Event-based Gateway ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Parallel Event-based Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;&lt;br/&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Gateways - Complex Gateway-01.png | 30px| alt=Complex Gateway ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''Complex Gateway'''&lt;/span&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div class=&quot;col-md-3&quot;&gt;<br /> <br /> &lt;div style=&quot;background-color: rgb(31, 153, 45); color: white; border-radius: 2px; padding-left: 5px; height: 30px; margin-bottom: 5px; padding-top: 5px; line-height: 1.3em;&quot;&gt;<br /> '''CONVERSATIONS'''<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot; style=&quot;margin-top: 10px;&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Multiple (Standard)-01.png | 30px ]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''A Conversation'''&lt;/span&gt;<br /> :defines a set of logically related message exchanges. When market with a '''(+)''' symbol it indicates a Sub-Conversation, a compound conversation element.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:LEAD BPMN 2.0 - Visio Stencils - Events - Multiple (Standard)-01.png | 30px | alt=A Call Conversation]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''A Call Conversation'''&lt;/span&gt;<br /> :is a wrapper for a globally defined Conversation of Sub-Conversation. A call to a Sub-Conversation is market with a '''(+)''' symbol.<br /> &lt;/div&gt;<br /> &lt;div class=&quot;media-notations&quot;&gt;&lt;span style=&quot;display:block; float: left; margin-right: 6px;&quot;&gt;[[ Image:Link-01.png | 30px | alt=A Conversation Link]]&lt;/span&gt;&lt;span class=&quot;icons-text&quot;&gt;'''A Conversation Link'''&lt;/span&gt;<br /> :connects Conversations And Participants.<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> [[ Image:XPMN.png |1500px]]<br /> [[Category:Objects]]<br /> {{DISPLAYTITLE:X-BPMN Notations}}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:Automated_Task-01.png&diff=1253 2015-08-28T12:59:56Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:Ad_Hoc_Marker-01.png&diff=1251 2015-08-28T12:57:34Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:User_Task-01.png&diff=1250 2015-08-28T12:55:38Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=Objects:BPMN_2.0_versus_eXtended_BPMN_(X-BPMN)&diff=917 2015-07-20T14:03:51Z

<p>Fbajohr: Lubo moved page Objects:X-BPMN Notations to Objects:BPMN 2.0 versus eXtended BPMN (X-BPMN)</p> <hr /> <div>'''Business Process Representation'''Business process modelling is the discipline of graphically representing a process into a readable diagram. The Business Process Modelling Notation (BPMN) is a graphical notation that depicts the steps in an end to end flow of a business process. The notation has been specifically designed to coordinate the sequence of processes and the messages that flow between different process participants in a related set of activities. BPMN is a vendor neutral, world-wide accepted standard managed by the Object Management Group (OMG) that provides a common way to model business processes. It offers both the simplicity and complexity required to model business processes for both the business audience as well as the technical audience. The LEAD Process Mapping standards is released as a part of the LEADing Practices and will be subject to continuous improvement and development.<br /> <br /> &lt;br/&gt;<br /> <br /> '''History of Business Process Modelling Notations'''<br /> <br /> • March 2001: BPMI members began discussing the idea of creating a notation to go along with the executable BPML. <br /> <br /> • August 2004: BPMN 1.0 specification was released to the public.<br /> • Now maintained by the Object Management Group (OMG). <br /> <br /> • January 2011: BPMN 2.0 specification was released to the public. <br /> <br /> &lt;br/&gt;<br /> <br /> '''LEADing Practice''' then further developed upon the BPMN 2.0 specification to include linkage to: <br /> <br /> • Business Competencies (January 2011). <br /> <br /> • Service Mapping (January 2011). <br /> <br /> • Interaction Models (March 2011). <br /> <br /> • RACI Mapping (May 2011). <br /> <br /> • Value Mapping (November 2011). <br /> <br /> • SAP Netweaver connection (January 2012). <br /> <br /> • SAP Solution Manager connection (February 2012). <br /> <br /> • Incorporation of LEAD X-BPMN principles into iGrafx (November 2012).<br /> <br /> BPMN 2.0 versus eXtended BPMN (X-BPMN) Process Modelling<br /> <br /> {| class=&quot;wikitable&quot; <br /> |+ <br /> |- <br /> ! BPMN 2.0 !! X-BPMN !! Source !! scope=&quot;col&quot; width=&quot;75%&quot; | Description <br /> <br /> |- <br /> ||| [[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Rule-01.png | 30px ]] <br /> Rule <br /> <br /> || [[ Image:Leadin.png | 100px]] <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> <br /> [[ Image:Logo ibm.png | 100px]] <br /> <br /> IBM WebSphere<br /> <br /> <br /> [[ Image:Microsoft.png | 100px]] <br /> <br /> Microsoft .NET <br /> || A '''Rule''' is a statement describing a business policy or decision procedure. Some programming languages run business rules<br /> together in very complex algorithms. In business process analysis, each rule is usually stated independently, in the general<br /> format of: If A and B, Then C.<br /> <br /> Workflow tools and detailed process diagrams both depend on business rules to specify how decisions are made. We generally associate business rules with activities. A decision table is adequate to show what happens if A or B happens, but dozens<br /> or even hundreds of business rules may need to be defined to clarify if A or B should happen. Training programs, job aids,<br /> software systems, and knowledge management systems aim to document business rules either to automate the decision<br /> process or to and make the rules available to other decision makers.<br /> <br /> A '''Rule''' is a set of conditions and associated actions that are performed when the conditions are satisfied. Rules can be written<br /> in two forms: as If and Then-statements, and as Decision Tables.<br /> <br /> Business '''Rules''' are statements that describe business policies or describe key business decisions.<br /> <br /> An action '''Rule''' is made of a condition part and of an action part. The first part of the rule defines the condition in which the<br /> rule applies. The second part of the rule defines the action to take if the condition of the rule is true.<br /> <br /> A '''Rule''' defines a condition with an associated set of actions to perform. Rules can be related to:<br /> <br /> • Active: Gets or sets a value that indicates whether the Rule should be evaluated.<br /> <br /> • Condition: Gets or sets a RuleCondition for the Rule to evaluate.<br /> <br /> • Description: Gets or sets a description of the Rule.<br /> <br /> • ElseActions: Gets a collection of RuleAction classes to perform in the ELSE case.<br /> <br /> • Name: Gets or sets the name of the Rule.<br /> <br /> • Priority: Gets or sets a value that indicates the order in which a Rule should be run.<br /> <br /> • Reevaluation: Behavior gets or sets a value indicating whether a Rule can be reevaluated.<br /> <br /> • ThenActions: Gets a collection of RuleAction classes to perform in the THEN case.<br /> |-<br /> |<br /> | [[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Flow_Ruleset-01.png | 30px]] <br /> Flow Ruleset <br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> | A '''Flow Ruleset''' is a collection (and thereby grouping) of rules that apply to a flow. These flow rulesets are either grouped<br /> based on common related rules in the flow, decisions tables, or the need to govern a specific set or behavior of tasks in the<br /> flow. Grouping such flow rulesets allows for sharing of rules and execution, by a rule engine throughout the entire flow. As<br /> well as the relation to the reuse of such rulsets in other flows, starting from the main flow where the ruleset are applied.<br /> <br /> A '''Flow Ruleset''' is a ruleset that allows you to group business rules that need to be executed as in a flow chart. It always has<br /> one flow, designated as main flow, besides possibly many other rule flows. The execution of the Flow Ruleset starts with the<br /> main flow. A Flow Ruleset consists of: Aliases, Definition, Rule Flow, Rule Scripts, If-Then Rules and Decision Tables.<br /> |-<br /> |<br /> |[[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Notification-01.png | 30px]]<br /> <br /> Notification<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> |An instance of a message delivered to one or more recipients. A '''Notification''' activity sends a message to a user, both the<br /> recipients and the content that needs to be specified. Notification activities furthermore allow flow rulesets to be applied in<br /> order to notify users of events that occur during the workflow.<br /> <br /> A '''Notification''' provides often through technology a means of delivering a message to a set of recipients. One need to specify<br /> the recipients and then parameterize the subject and message that are sent.<br /> <br /> The '''Notification''' task allows you to send different types of notifications to the users of the application.<br /> |-<br /> |<br /> |[[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Mapping-01.png | 30px]]<br /> Mapping<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> |'''Mapping''' activities includes identifying, defining and plotting the involved business, information and data objects within the<br /> activities. This allows to identify possible grouping of common business, information and data objects and their associated<br /> rules (e.g. rulesets), enabling the change of complex objects and views into more simple views.<br /> <br /> A '''Mapping''' activity can be used to transform complex objects into more simple views (e.g. map data from data objects in the<br /> specific process context making it more simple data). Rules set can be used as a transform in a mapping activity. To make the<br /> mapping activity work, the mappings between the business, information and data objects in the process context needs to be<br /> defined.<br /> |-<br /> |<br /> | [[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Reporting-01.png | 30px]]<br /> Reporting<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> |'''Reporting''' is the exposure, description and portrayment of specific tasks, services and the associated information and data. The information and data objects/source can bind with the reporting activity the process components to the specific cockpits,<br /> dashboards or scorecards.<br /> <br /> To illustrate and express what is happening, or what has already happened, includes timely collection, analysis and then reporting of the information within the process. Depending if it is real time reporting or after the fact reporting, the input mapping needs to be specified.<br /> <br /> A '''Reporting''' activity is used to collect data and information in order to perform analytics on this data. The reporting activity<br /> references a reporting data source and indicates where in the process data is gathered for reporting. An input mapping<br /> needs to be defined for the reporting activity to specify which data from the process context is collected by the reporting<br /> activity.<br /> |-<br /> |<br /> |icon<br /> <br /> Business Object<br /> <br /> icon<br /> <br /> Collection of <br /> <br /> Business objects<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> |A '''Business Object''' is the term used to express real-world objects like people, employee, products or a sales order, customer and revenue. Business Objects used for example in business, process and service mapping and furthermore used in application<br /> implementations where they are used as a patented semantic layer that shields users from the complexities of information<br /> table names and data relationships.<br /> <br /> Below is a list of the different kinds of Business Objects that are commonly used in business modeling, process mapping and service mapping as well as in application and/or architectural mapping (e.g. business architecture, application architecture<br /> and solution architecture):<br /> <br /> • '''Business Object''' - Represents real-world objects like people, employee, products or a sales order, customer and revenue.<br /> <br /> • '''Collection of Business Objects''' - Represents a collection of real-world objects, e.g. a employee roles.<br /> <br /> • '''Business Input''' - Is an external input for the real-world objects. A kind of input parameter<br /> <br /> • '''Business Output''' - Is the real-world result of the entire process and or service flow. A kind of output parameter.<br /> <br /> • '''Business Store''' - Is a place where the real-world objects are stored.<br /> |-<br /> |<br /> |icon<br /> Information Object<br /> <br /> Collection of<br /> <br /> Information Objects<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> |An '''Information Object''' is used to specify information about real-world objects (like people, employees, products or a sales order, etc.), and is therefore a digital representation of an existing entity within an Information System (e.g. Oracle ERP or SAP<br /> ERP). It encompasses both the business information (in the form of functions and methods) and the application information (in the form of attributes) of the entity. Information Objects can be found and therefore modeled in business functions, business services and business processes.<br /> <br /> Below is a list of the different kinds of Information Objects used in business modeling, process mapping and service mapping as well as in application and/or architectural mapping (e.g. business architecture, information architecture, application architecture and solution architecture):<br /> <br /> • '''Information Object''' - Represents a container of information within the flow of the process and or service, such as business<br /> documents, e-mails, or letters.<br /> <br /> &lt;nowiki&gt; &lt;/nowiki&gt;• '''Collection of Information Objects''' - Represents a collection of information (e.g. a list of order items).<br /> <br /> • '''Information Input''' - Is an external information input for the entire process. A kind of input parameter.<br /> <br /> • '''Information Output''' - Is the information output/result of the entire process. A kind of output parameter.<br /> <br /> • '''Information Store''' - Is a place where the information can be read or written (e.g. knowledge management or a filing cabinet). It persists beyond the lifetime of the process instance.<br /> |-<br /> |<br /> |icon<br /> Data Object<br /> <br /> icon<br /> <br /> Collection of <br /> <br /> Data objects<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> |A Data Object is a logical cluster of all tables in the data set that have one or more columns containing data related to the same business entity. Data objects are not maps, but instead represent an object view of related Information Objects and they represent Business Objects.<br /> <br /> Below is a list of the different kinds of Data Objects used in process mapping and service mapping as well as in application<br /> and/or architectural mapping (e.g. information architecture, application architecture, solution architecture and data architecture):<br /> <br /> • '''Data Object''' - Represents a container/logical cluster of all tables in the data set that have one or more columns containing data related to the same data entity, such as business documents, e-mails, or letters.<br /> <br /> • '''Collection of Data Objects''' - Represents a collection of data tables/columns containing data related to the same data entity (e.g. a list of order items).<br /> <br /> • '''Data Input''' - Is an external data input for the entire process. A kind of input parameter.<br /> <br /> • '''Data Output''' - Is the data result of the entire process. A kind of output parameter.<br /> <br /> • '''Data Store''' - Is a place where the process can read or write data (e.g. a database or a filing cabinet). It persists beyond the lifetime of the process instance.<br /> |-<br /> |None<br /> |None<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |No special task type is indicated.<br /> |-<br /> |icon<br /> User<br /> |icon<br /> User<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''User Task''' is a typical “workflow” task where a human performer performs the task with the assistance of a software application<br /> and is scheduled through a task list manager of some sort.<br /> |-<br /> |icon<br /> Manual<br /> |icon<br /> Manual Task<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Manual Task''' is a task that is expected to be performed without the aid of any business process execution engine or any<br /> application.<br /> |-<br /> |<br /> |icon<br /> Automated Task<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> |An '''Automated Task''' is an activity that is automated through either a business process execution engine or any application<br /> (e.g. using application features and/or functions to enable the application task).<br /> |-<br /> |icon<br /> Service<br /> |<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Service Task''' is a task that uses some sort of service which could be a web service or an automated application.<br /> |-<br /> |<br /> |icon<br /> Manual Service<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> |A '''Manual Service''' is when the service is performed by a human.<br /> |-<br /> |<br /> |icon<br /> <br /> Automated Service<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> |An '''Automated Service''' can be either an application service, data service, platform service, infrastructure service or a web<br /> service.<br /> |-<br /> |icon<br /> <br /> Send<br /> |icon<br /> <br /> Send<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Send Task''' is a simple task that is designed to send a message to an external participant (relative to the process).<br /> |-<br /> |icon<br /> <br /> Receive<br /> |icon<br /> <br /> Receive<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Receive Tas'''k is a simple task that is designed to wait for a message to arrive from an external participant (relative to the<br /> process).<br /> |-<br /> |icon<br /> <br /> Script<br /> |icon<br /> <br /> Script<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Script Task''' is executed by a business process engine. The modeler or implementer defines a script in a language that the<br /> engine can interpret, and when the task is ready to start, the engine will execute the script. When the script is completed, the<br /> task will also be completed.<br /> |-<br /> |icon<br /> <br /> Business Rule<br /> |icon<br /> <br /> Business Rule<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Business Rule Task''' provides a mechanism for the process to provide input to a business rules engine, and to get the output<br /> of calculations that the business rules engine might provide. The input/output specification of the task will allow the process<br /> to send data to and receive data from the business rules engine.<br /> |-<br /> |<br /> |icon<br /> <br /> Ruleset<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> <br /> [[ Image:Logo ibm.png | 100px]] <br /> <br /> IBM WebSphere<br /> <br /> [[ Image:Microsoft.png | 100px]] <br /> <br /> Microsoft .NET<br /> |A '''Ruleset''' is a collection (and thereby a grouping) of rules. They are either grouped based on common related rules, decisions tables or the need to govern a specific set or behavior of tasks. Grouping such rulesets allows for sharing of rules and execution by a rules engine.<br /> <br /> A '''Ruleset''' is a logical collection of rules. A ruleset helps you group business rules that govern a specific function. A ruleset<br /> consists of: If-Then Rules and Decision Tables.<br /> <br /> A '''Ruleset''' is a container that includes definitions for a group of related rules and decision tables. A ruleset provides a unit of<br /> execution for rules and for Decision Tables. In addition, rulesets provide a unit of sharing for rules; rules belong to a ruleset.<br /> <br /> A '''Ruleset''' is a set of rules and rule artifacts that can be executed by the engine.<br /> <br /> A '''Ruleset''' contains a collection of rule classes along with the semantics for forward-chaining execution of those rules. A Ruleset<br /> can be executed directly in code or by using the Policy Activity activity<br /> |-<br /> |<br /> |icon<br /> <br /> Decision Table<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> <br /> [[ Image:Logo ibm.png | 100px]] <br /> <br /> IBM WebSphere<br /> <br /> [[ Image:Microsoft.png | 100px]] <br /> <br /> Microsoft .NET<br /> |A '''Decision Table''' defines decisions based on a number of given conditions and actions. Decision tables allow to work from<br /> the same information, and are therefore a precise way to model complicated logics and associations.<br /> <br /> A '''Decision Table''' can either be a tabular representation of related rules or a precise yet compact way to map complicated logic. Decision tables, like flowcharts and if-then-else and switch-case statements, associate conditions with actions to perform, but in many cases do so in a more elegant way.<br /> <br /> An example of using a '''Decision Table''' is an activity to evaluate based on the region and the total amount of the order, whether<br /> or not the approval of a supervisor is required or not. Would be good to have this as a reusable task instead of embedded in<br /> the gateway. The gateway can then just do the branching. Could include a link to a spreadsheet for example.<br /> <br /> '''Decision Tables''' provide an alternative way of viewing and managing large sets of symmetric business rules. A decision table<br /> contains condition columns and action columns.<br /> <br /> '''Decision Tables''' are a simple and clean method of representing large sets of business rules<br /> |-<br /> |<br /> |icon <br /> <br /> Rule Script<br /> |<br /> <br /> [[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> <br /> [[ Image:Logo ibm.png | 100px]] <br /> <br /> IBM WebSphere<br /> |'''Rule Flows''' are comprised of linked tasks that contain the instructions for which rules to execute and in what order. The rules are organized into tasks, and the rule flow specifies how tasks are chained together; how, when, and under what conditions<br /> they are executed. When you are dealing with many large rulesets, managing the order in which rules are evaluated can become complex. Rule flows allows you to specify the order in which rulesets are to be evaluated. It does so by providing you with a flow chart. Use this chart to define which rule sets should be evaluated in sequence, and which ones in parallel, and to specify conditions under which rule sets should be evaluated. The reuse of rules components and their natural relations like activity association are an important aspect of rule modelling principles. This allows for rule modelling consistency between the different rule artifacts from the rule flows, rule scripts, rulesets, flow rulesets, rules and decision tables.<br /> <br /> In order to do advanced project or business area rule modelling, it might be necessary to categorize some of the rules into<br /> main and sub rules. A project can contain many rule flows, one of which must be identified as the main rule flow of the project or area. Additional rule flows could then be added and modelled from the main rule flow. Other rule flows are then included through sub flow tasks.<br /> <br /> A '''Rule Flow''' is a sequence of activities for evaluating business rules. The order of the execution of the rules is diagrammatically<br /> represented in the form of a flow chart. It is a reusable entity within a flow ruleset, and is based on activities associated with artifacts such as rule scripts, rule flows, rulesets, flow rulesets, rules and decision tables.<br /> <br /> Multiple rulesets can be executed in order. This is called a '''Rule Flow'''. The ruleset stack determines the order. The order can be manipulated by rule actions that push and pop rulesets on the stack. In rulesets, the priority of rules applies to specify the order of firing of the rules in the ruleset. Rulesets also provide an effective date specification that identifies that the ruleset is always active, or that the ruleset is restricted based on a time and date range, or a starting or ending time and date.<br /> <br /> A '''Rule Flow''' defines the flow of execution of the rules. The rules are organized into tasks and the ruleflow specifies how tasks<br /> are chained together; how, when, and under what conditions they are executed.<br /> |-<br /> |<br /> |icon<br /> <br /> Rule Script<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> [[ Image:Microsoft.png | 100px]] <br /> <br /> Microsoft .NET<br /> |A '''Rule Script''' allows generating a rule in a scripting environment. This is done through the connection of other activities and the rules that govern these relations, and the actions between them. Rule scripts can furthermore be used with script types, and thereby automated test rules (e.g. configurable, programmed, query and event-based network alerts). The link between rule scripts and the mentioned script type could be used as template–based query that can be run against backend tables or database views.<br /> <br /> A '''Rule Script''' is a reusable artifact within a flow ruleset and is a sequence of actions. It is associated with other activities in a flow ruleset, and is triggered when the conditions listed in the preceding activities are satisfied.<br /> <br /> A rule script can contain any of the following action types: Assign Action, Assert Action, Evaluate Decision, Table Action,<br /> Execute Action, Execute Ruleset Action, Execute Rule Action, For Each Action, If Else, If Action, While Action, Retract Action, Break and Continue Actions.<br /> <br /> The '''Rule Script''' allows to generate a rule from a scripting environment.<br /> |}<br /> [[Category:Objects]]<br /> {{DISPLAYTITLE:BPMN 2.0 versus eXtended BPMN (X-BPMN)}}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=Objects:BPMN_2.0_versus_eXtended_BPMN_(X-BPMN)&diff=916 2015-07-20T13:59:27Z

<p>Fbajohr: </p> <hr /> <div>'''Business Process Representation'''Business process modelling is the discipline of graphically representing a process into a readable diagram. The Business Process Modelling Notation (BPMN) is a graphical notation that depicts the steps in an end to end flow of a business process. The notation has been specifically designed to coordinate the sequence of processes and the messages that flow between different process participants in a related set of activities. BPMN is a vendor neutral, world-wide accepted standard managed by the Object Management Group (OMG) that provides a common way to model business processes. It offers both the simplicity and complexity required to model business processes for both the business audience as well as the technical audience. The LEAD Process Mapping standards is released as a part of the LEADing Practices and will be subject to continuous improvement and development.<br /> <br /> &lt;br/&gt;<br /> <br /> '''History of Business Process Modelling Notations'''<br /> <br /> • March 2001: BPMI members began discussing the idea of creating a notation to go along with the executable BPML. <br /> <br /> • August 2004: BPMN 1.0 specification was released to the public.<br /> • Now maintained by the Object Management Group (OMG). <br /> <br /> • January 2011: BPMN 2.0 specification was released to the public. <br /> <br /> &lt;br/&gt;<br /> <br /> '''LEADing Practice''' then further developed upon the BPMN 2.0 specification to include linkage to: <br /> <br /> • Business Competencies (January 2011). <br /> <br /> • Service Mapping (January 2011). <br /> <br /> • Interaction Models (March 2011). <br /> <br /> • RACI Mapping (May 2011). <br /> <br /> • Value Mapping (November 2011). <br /> <br /> • SAP Netweaver connection (January 2012). <br /> <br /> • SAP Solution Manager connection (February 2012). <br /> <br /> • Incorporation of LEAD X-BPMN principles into iGrafx (November 2012).<br /> <br /> BPMN 2.0 versus eXtended BPMN (X-BPMN) Process Modelling<br /> <br /> {| class=&quot;wikitable&quot; <br /> |+ <br /> |- <br /> ! BPMN 2.0 !! X-BPMN !! Source !! scope=&quot;col&quot; width=&quot;75%&quot; | Description <br /> <br /> |- <br /> ||| [[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Rule-01.png | 30px ]] <br /> Rule <br /> <br /> || [[ Image:Leadin.png | 100px]] <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> <br /> [[ Image:Logo ibm.png | 100px]] <br /> <br /> IBM WebSphere<br /> <br /> <br /> [[ Image:Microsoft.png | 100px]] <br /> <br /> Microsoft .NET <br /> || A '''Rule''' is a statement describing a business policy or decision procedure. Some programming languages run business rules<br /> together in very complex algorithms. In business process analysis, each rule is usually stated independently, in the general<br /> format of: If A and B, Then C.<br /> <br /> Workflow tools and detailed process diagrams both depend on business rules to specify how decisions are made. We generally associate business rules with activities. A decision table is adequate to show what happens if A or B happens, but dozens<br /> or even hundreds of business rules may need to be defined to clarify if A or B should happen. Training programs, job aids,<br /> software systems, and knowledge management systems aim to document business rules either to automate the decision<br /> process or to and make the rules available to other decision makers.<br /> <br /> A '''Rule''' is a set of conditions and associated actions that are performed when the conditions are satisfied. Rules can be written<br /> in two forms: as If and Then-statements, and as Decision Tables.<br /> <br /> Business '''Rules''' are statements that describe business policies or describe key business decisions.<br /> <br /> An action '''Rule''' is made of a condition part and of an action part. The first part of the rule defines the condition in which the<br /> rule applies. The second part of the rule defines the action to take if the condition of the rule is true.<br /> <br /> A '''Rule''' defines a condition with an associated set of actions to perform. Rules can be related to:<br /> <br /> • Active: Gets or sets a value that indicates whether the Rule should be evaluated.<br /> <br /> • Condition: Gets or sets a RuleCondition for the Rule to evaluate.<br /> <br /> • Description: Gets or sets a description of the Rule.<br /> <br /> • ElseActions: Gets a collection of RuleAction classes to perform in the ELSE case.<br /> <br /> • Name: Gets or sets the name of the Rule.<br /> <br /> • Priority: Gets or sets a value that indicates the order in which a Rule should be run.<br /> <br /> • Reevaluation: Behavior gets or sets a value indicating whether a Rule can be reevaluated.<br /> <br /> • ThenActions: Gets a collection of RuleAction classes to perform in the THEN case.<br /> |-<br /> |<br /> | [[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Flow_Ruleset-01.png | 30px]] <br /> Flow Ruleset <br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> | A '''Flow Ruleset''' is a collection (and thereby grouping) of rules that apply to a flow. These flow rulesets are either grouped<br /> based on common related rules in the flow, decisions tables, or the need to govern a specific set or behavior of tasks in the<br /> flow. Grouping such flow rulesets allows for sharing of rules and execution, by a rule engine throughout the entire flow. As<br /> well as the relation to the reuse of such rulsets in other flows, starting from the main flow where the ruleset are applied.<br /> <br /> A '''Flow Ruleset''' is a ruleset that allows you to group business rules that need to be executed as in a flow chart. It always has<br /> one flow, designated as main flow, besides possibly many other rule flows. The execution of the Flow Ruleset starts with the<br /> main flow. A Flow Ruleset consists of: Aliases, Definition, Rule Flow, Rule Scripts, If-Then Rules and Decision Tables.<br /> |-<br /> |<br /> |[[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Notification-01.png | 30px]]<br /> <br /> Notification<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> |An instance of a message delivered to one or more recipients. A '''Notification''' activity sends a message to a user, both the<br /> recipients and the content that needs to be specified. Notification activities furthermore allow flow rulesets to be applied in<br /> order to notify users of events that occur during the workflow.<br /> <br /> A '''Notification''' provides often through technology a means of delivering a message to a set of recipients. One need to specify<br /> the recipients and then parameterize the subject and message that are sent.<br /> <br /> The '''Notification''' task allows you to send different types of notifications to the users of the application.<br /> |-<br /> |<br /> |[[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Mapping-01.png | 30px]]<br /> Mapping<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> |'''Mapping''' activities includes identifying, defining and plotting the involved business, information and data objects within the<br /> activities. This allows to identify possible grouping of common business, information and data objects and their associated<br /> rules (e.g. rulesets), enabling the change of complex objects and views into more simple views.<br /> <br /> A '''Mapping''' activity can be used to transform complex objects into more simple views (e.g. map data from data objects in the<br /> specific process context making it more simple data). Rules set can be used as a transform in a mapping activity. To make the<br /> mapping activity work, the mappings between the business, information and data objects in the process context needs to be<br /> defined.<br /> |-<br /> |<br /> | [[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Reporting-01.png | 30px]]<br /> Reporting<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> |'''Reporting''' is the exposure, description and portrayment of specific tasks, services and the associated information and data. The information and data objects/source can bind with the reporting activity the process components to the specific cockpits,<br /> dashboards or scorecards.<br /> <br /> To illustrate and express what is happening, or what has already happened, includes timely collection, analysis and then reporting of the information within the process. Depending if it is real time reporting or after the fact reporting, the input mapping needs to be specified.<br /> <br /> A '''Reporting''' activity is used to collect data and information in order to perform analytics on this data. The reporting activity<br /> references a reporting data source and indicates where in the process data is gathered for reporting. An input mapping<br /> needs to be defined for the reporting activity to specify which data from the process context is collected by the reporting<br /> activity.<br /> |-<br /> |<br /> |icon<br /> <br /> Business Object<br /> <br /> icon<br /> <br /> Collection of <br /> <br /> Business objects<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> |A '''Business Object''' is the term used to express real-world objects like people, employee, products or a sales order, customer and revenue. Business Objects used for example in business, process and service mapping and furthermore used in application<br /> implementations where they are used as a patented semantic layer that shields users from the complexities of information<br /> table names and data relationships.<br /> <br /> Below is a list of the different kinds of Business Objects that are commonly used in business modeling, process mapping and service mapping as well as in application and/or architectural mapping (e.g. business architecture, application architecture<br /> and solution architecture):<br /> <br /> • '''Business Object''' - Represents real-world objects like people, employee, products or a sales order, customer and revenue.<br /> <br /> • '''Collection of Business Objects''' - Represents a collection of real-world objects, e.g. a employee roles.<br /> <br /> • '''Business Input''' - Is an external input for the real-world objects. A kind of input parameter<br /> <br /> • '''Business Output''' - Is the real-world result of the entire process and or service flow. A kind of output parameter.<br /> <br /> • '''Business Store''' - Is a place where the real-world objects are stored.<br /> |-<br /> |<br /> |icon<br /> Information Object<br /> <br /> Collection of<br /> <br /> Information Objects<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> |An '''Information Object''' is used to specify information about real-world objects (like people, employees, products or a sales order, etc.), and is therefore a digital representation of an existing entity within an Information System (e.g. Oracle ERP or SAP<br /> ERP). It encompasses both the business information (in the form of functions and methods) and the application information (in the form of attributes) of the entity. Information Objects can be found and therefore modeled in business functions, business services and business processes.<br /> <br /> Below is a list of the different kinds of Information Objects used in business modeling, process mapping and service mapping as well as in application and/or architectural mapping (e.g. business architecture, information architecture, application architecture and solution architecture):<br /> <br /> • '''Information Object''' - Represents a container of information within the flow of the process and or service, such as business<br /> documents, e-mails, or letters.<br /> <br /> &lt;nowiki&gt; &lt;/nowiki&gt;• '''Collection of Information Objects''' - Represents a collection of information (e.g. a list of order items).<br /> <br /> • '''Information Input''' - Is an external information input for the entire process. A kind of input parameter.<br /> <br /> • '''Information Output''' - Is the information output/result of the entire process. A kind of output parameter.<br /> <br /> • '''Information Store''' - Is a place where the information can be read or written (e.g. knowledge management or a filing cabinet). It persists beyond the lifetime of the process instance.<br /> |-<br /> |<br /> |icon<br /> Data Object<br /> <br /> icon<br /> <br /> Collection of <br /> <br /> Data objects<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> |A Data Object is a logical cluster of all tables in the data set that have one or more columns containing data related to the same business entity. Data objects are not maps, but instead represent an object view of related Information Objects and they represent Business Objects.<br /> <br /> Below is a list of the different kinds of Data Objects used in process mapping and service mapping as well as in application<br /> and/or architectural mapping (e.g. information architecture, application architecture, solution architecture and data architecture):<br /> <br /> • '''Data Object''' - Represents a container/logical cluster of all tables in the data set that have one or more columns containing data related to the same data entity, such as business documents, e-mails, or letters.<br /> <br /> • '''Collection of Data Objects''' - Represents a collection of data tables/columns containing data related to the same data entity (e.g. a list of order items).<br /> <br /> • '''Data Input''' - Is an external data input for the entire process. A kind of input parameter.<br /> <br /> • '''Data Output''' - Is the data result of the entire process. A kind of output parameter.<br /> <br /> • '''Data Store''' - Is a place where the process can read or write data (e.g. a database or a filing cabinet). It persists beyond the lifetime of the process instance.<br /> |-<br /> |None<br /> |None<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |No special task type is indicated.<br /> |-<br /> |icon<br /> User<br /> |icon<br /> User<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''User Task''' is a typical “workflow” task where a human performer performs the task with the assistance of a software application<br /> and is scheduled through a task list manager of some sort.<br /> |-<br /> |icon<br /> Manual<br /> |icon<br /> Manual Task<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Manual Task''' is a task that is expected to be performed without the aid of any business process execution engine or any<br /> application.<br /> |-<br /> |<br /> |icon<br /> Automated Task<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> |An '''Automated Task''' is an activity that is automated through either a business process execution engine or any application<br /> (e.g. using application features and/or functions to enable the application task).<br /> |-<br /> |icon<br /> Service<br /> |<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Service Task''' is a task that uses some sort of service which could be a web service or an automated application.<br /> |-<br /> |<br /> |icon<br /> Manual Service<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> |A '''Manual Service''' is when the service is performed by a human.<br /> |-<br /> |<br /> |icon<br /> <br /> Automated Service<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> |An '''Automated Service''' can be either an application service, data service, platform service, infrastructure service or a web<br /> service.<br /> |-<br /> |icon<br /> <br /> Send<br /> |icon<br /> <br /> Send<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Send Task''' is a simple task that is designed to send a message to an external participant (relative to the process).<br /> |-<br /> |icon<br /> <br /> Receive<br /> |icon<br /> <br /> Receive<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Receive Tas'''k is a simple task that is designed to wait for a message to arrive from an external participant (relative to the<br /> process).<br /> |-<br /> |icon<br /> <br /> Script<br /> |icon<br /> <br /> Script<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Script Task''' is executed by a business process engine. The modeler or implementer defines a script in a language that the<br /> engine can interpret, and when the task is ready to start, the engine will execute the script. When the script is completed, the<br /> task will also be completed.<br /> |-<br /> |icon<br /> <br /> Business Rule<br /> |icon<br /> <br /> Business Rule<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Business Rule Task''' provides a mechanism for the process to provide input to a business rules engine, and to get the output<br /> of calculations that the business rules engine might provide. The input/output specification of the task will allow the process<br /> to send data to and receive data from the business rules engine.<br /> |-<br /> |<br /> |icon<br /> <br /> Ruleset<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> <br /> [[ Image:Logo ibm.png | 100px]] <br /> <br /> IBM WebSphere<br /> <br /> [[ Image:Microsoft.png | 100px]] <br /> <br /> Microsoft .NET<br /> |A '''Ruleset''' is a collection (and thereby a grouping) of rules. They are either grouped based on common related rules, decisions tables or the need to govern a specific set or behavior of tasks. Grouping such rulesets allows for sharing of rules and execution by a rules engine.<br /> <br /> A '''Ruleset''' is a logical collection of rules. A ruleset helps you group business rules that govern a specific function. A ruleset<br /> consists of: If-Then Rules and Decision Tables.<br /> <br /> A '''Ruleset''' is a container that includes definitions for a group of related rules and decision tables. A ruleset provides a unit of<br /> execution for rules and for Decision Tables. In addition, rulesets provide a unit of sharing for rules; rules belong to a ruleset.<br /> <br /> A '''Ruleset''' is a set of rules and rule artifacts that can be executed by the engine.<br /> <br /> A '''Ruleset''' contains a collection of rule classes along with the semantics for forward-chaining execution of those rules. A Ruleset<br /> can be executed directly in code or by using the Policy Activity activity<br /> |-<br /> |<br /> |icon<br /> <br /> Decision Table<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> <br /> [[ Image:Logo ibm.png | 100px]] <br /> <br /> IBM WebSphere<br /> <br /> [[ Image:Microsoft.png | 100px]] <br /> <br /> Microsoft .NET<br /> |A '''Decision Table''' defines decisions based on a number of given conditions and actions. Decision tables allow to work from<br /> the same information, and are therefore a precise way to model complicated logics and associations.<br /> <br /> A '''Decision Table''' can either be a tabular representation of related rules or a precise yet compact way to map complicated logic. Decision tables, like flowcharts and if-then-else and switch-case statements, associate conditions with actions to perform, but in many cases do so in a more elegant way.<br /> <br /> An example of using a '''Decision Table''' is an activity to evaluate based on the region and the total amount of the order, whether<br /> or not the approval of a supervisor is required or not. Would be good to have this as a reusable task instead of embedded in<br /> the gateway. The gateway can then just do the branching. Could include a link to a spreadsheet for example.<br /> <br /> '''Decision Tables''' provide an alternative way of viewing and managing large sets of symmetric business rules. A decision table<br /> contains condition columns and action columns.<br /> <br /> '''Decision Tables''' are a simple and clean method of representing large sets of business rules<br /> |-<br /> |<br /> |icon <br /> <br /> Rule Script<br /> |<br /> <br /> [[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> <br /> [[ Image:Logo ibm.png | 100px]] <br /> <br /> IBM WebSphere<br /> |'''Rule Flows''' are comprised of linked tasks that contain the instructions for which rules to execute and in what order. The rules are organized into tasks, and the rule flow specifies how tasks are chained together; how, when, and under what conditions<br /> they are executed. When you are dealing with many large rulesets, managing the order in which rules are evaluated can become complex. Rule flows allows you to specify the order in which rulesets are to be evaluated. It does so by providing you with a flow chart. Use this chart to define which rule sets should be evaluated in sequence, and which ones in parallel, and to specify conditions under which rule sets should be evaluated. The reuse of rules components and their natural relations like activity association are an important aspect of rule modelling principles. This allows for rule modelling consistency between the different rule artifacts from the rule flows, rule scripts, rulesets, flow rulesets, rules and decision tables.<br /> <br /> In order to do advanced project or business area rule modelling, it might be necessary to categorize some of the rules into<br /> main and sub rules. A project can contain many rule flows, one of which must be identified as the main rule flow of the project or area. Additional rule flows could then be added and modelled from the main rule flow. Other rule flows are then included through sub flow tasks.<br /> <br /> A '''Rule Flow''' is a sequence of activities for evaluating business rules. The order of the execution of the rules is diagrammatically<br /> represented in the form of a flow chart. It is a reusable entity within a flow ruleset, and is based on activities associated with artifacts such as rule scripts, rule flows, rulesets, flow rulesets, rules and decision tables.<br /> <br /> Multiple rulesets can be executed in order. This is called a '''Rule Flow'''. The ruleset stack determines the order. The order can be manipulated by rule actions that push and pop rulesets on the stack. In rulesets, the priority of rules applies to specify the order of firing of the rules in the ruleset. Rulesets also provide an effective date specification that identifies that the ruleset is always active, or that the ruleset is restricted based on a time and date range, or a starting or ending time and date.<br /> <br /> A '''Rule Flow''' defines the flow of execution of the rules. The rules are organized into tasks and the ruleflow specifies how tasks<br /> are chained together; how, when, and under what conditions they are executed.<br /> |-<br /> |<br /> |icon<br /> <br /> Rule Script<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> [[ Image:Microsoft.png | 100px]] <br /> <br /> Microsoft .NET<br /> |A '''Rule Script''' allows generating a rule in a scripting environment. This is done through the connection of other activities and the rules that govern these relations, and the actions between them. Rule scripts can furthermore be used with script types, and thereby automated test rules (e.g. configurable, programmed, query and event-based network alerts). The link between rule scripts and the mentioned script type could be used as template–based query that can be run against backend tables or database views.<br /> <br /> A '''Rule Script''' is a reusable artifact within a flow ruleset and is a sequence of actions. It is associated with other activities in a flow ruleset, and is triggered when the conditions listed in the preceding activities are satisfied.<br /> <br /> A rule script can contain any of the following action types: Assign Action, Assert Action, Evaluate Decision, Table Action,<br /> Execute Action, Execute Ruleset Action, Execute Rule Action, For Each Action, If Else, If Action, While Action, Retract Action, Break and Continue Actions.<br /> <br /> The '''Rule Script''' allows to generate a rule from a scripting environment.<br /> |}<br /> [[Category:Objects]]<br /> {{DISPLAYTITLE:BPMN 2.0 versus eXtended BPMN (X-BPMN)}}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=Objects:BPMN_2.0_versus_eXtended_BPMN_(X-BPMN)&diff=915 2015-07-20T13:57:38Z

<p>Fbajohr: </p> <hr /> <div>'''Business Process Representation'''Business process modelling is the discipline of graphically representing a process into a readable diagram. The Business Process Modelling Notation (BPMN) is a graphical notation that depicts the steps in an end to end flow of a business process. The notation has been specifically designed to coordinate the sequence of processes and the messages that flow between different process participants in a related set of activities. BPMN is a vendor neutral, world-wide accepted standard managed by the Object Management Group (OMG) that provides a common way to model business processes. It offers both the simplicity and complexity required to model business processes for both the business audience as well as the technical audience. The LEAD Process Mapping standards is released as a part of the LEADing Practices and will be subject to continuous improvement and development.<br /> <br /> &lt;br/&gt;<br /> <br /> '''History of Business Process Modelling Notations'''<br /> <br /> • March 2001: BPMI members began discussing the idea of creating a notation to go along with the executable BPML. <br /> <br /> • August 2004: BPMN 1.0 specification was released to the public.<br /> • Now maintained by the Object Management Group (OMG). <br /> <br /> • January 2011: BPMN 2.0 specification was released to the public. <br /> <br /> &lt;br/&gt;<br /> <br /> '''LEADing Practice''' then further developed upon the BPMN 2.0 specification to include linkage to: <br /> <br /> • Business Competencies (January 2011). <br /> <br /> • Service Mapping (January 2011). <br /> <br /> • Interaction Models (March 2011). <br /> <br /> • RACI Mapping (May 2011). <br /> <br /> • Value Mapping (November 2011). <br /> <br /> • SAP Netweaver connection (January 2012). <br /> <br /> • SAP Solution Manager connection (February 2012). <br /> <br /> • Incorporation of LEAD X-BPMN principles into iGrafx (November 2012).<br /> <br /> BPMN 2.0 versus eXtended BPMN (X-BPMN) Process Modelling<br /> <br /> {| class=&quot;wikitable&quot; <br /> |+ <br /> |- <br /> ! BPMN 2.0 !! X-BPMN !! Source !! scope=&quot;col&quot; width=&quot;75%&quot; | Description <br /> <br /> |- <br /> ||| [[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Rule-01.png | 30px ]] <br /> Rule <br /> <br /> || [[ Image:Leadin.png | 100px]] <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> <br /> [[ Image:Logo ibm.png | 100px]] <br /> <br /> IBM WebSphere<br /> <br /> <br /> [[ Image:Microsoft.png | 100px]] <br /> <br /> Microsoft .NET <br /> || A '''Rule''' is a statement describing a business policy or decision procedure. Some programming languages run business rules<br /> together in very complex algorithms. In business process analysis, each rule is usually stated independently, in the general<br /> format of: If A and B, Then C.<br /> <br /> Workflow tools and detailed process diagrams both depend on business rules to specify how decisions are made. We generally associate business rules with activities. A decision table is adequate to show what happens if A or B happens, but dozens<br /> or even hundreds of business rules may need to be defined to clarify if A or B should happen. Training programs, job aids,<br /> software systems, and knowledge management systems aim to document business rules either to automate the decision<br /> process or to and make the rules available to other decision makers.<br /> <br /> A '''Rule''' is a set of conditions and associated actions that are performed when the conditions are satisfied. Rules can be written<br /> in two forms: as If and Then-statements, and as Decision Tables.<br /> <br /> Business '''Rules''' are statements that describe business policies or describe key business decisions.<br /> <br /> An action '''Rule''' is made of a condition part and of an action part. The first part of the rule defines the condition in which the<br /> rule applies. The second part of the rule defines the action to take if the condition of the rule is true.<br /> <br /> A '''Rule''' defines a condition with an associated set of actions to perform. Rules can be related to:<br /> <br /> • Active: Gets or sets a value that indicates whether the Rule should be evaluated.<br /> <br /> • Condition: Gets or sets a RuleCondition for the Rule to evaluate.<br /> <br /> • Description: Gets or sets a description of the Rule.<br /> <br /> • ElseActions: Gets a collection of RuleAction classes to perform in the ELSE case.<br /> <br /> • Name: Gets or sets the name of the Rule.<br /> <br /> • Priority: Gets or sets a value that indicates the order in which a Rule should be run.<br /> <br /> • Reevaluation: Behavior gets or sets a value indicating whether a Rule can be reevaluated.<br /> <br /> • ThenActions: Gets a collection of RuleAction classes to perform in the THEN case.<br /> |-<br /> |<br /> | [[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Flow_Ruleset-01.png | 30px]] <br /> Flow Ruleset <br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> | A '''Flow Ruleset''' is a collection (and thereby grouping) of rules that apply to a flow. These flow rulesets are either grouped<br /> based on common related rules in the flow, decisions tables, or the need to govern a specific set or behavior of tasks in the<br /> flow. Grouping such flow rulesets allows for sharing of rules and execution, by a rule engine throughout the entire flow. As<br /> well as the relation to the reuse of such rulsets in other flows, starting from the main flow where the ruleset are applied.<br /> <br /> A '''Flow Ruleset''' is a ruleset that allows you to group business rules that need to be executed as in a flow chart. It always has<br /> one flow, designated as main flow, besides possibly many other rule flows. The execution of the Flow Ruleset starts with the<br /> main flow. A Flow Ruleset consists of: Aliases, Definition, Rule Flow, Rule Scripts, If-Then Rules and Decision Tables.<br /> |-<br /> |<br /> |[[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Notification-01.png | 30px]]<br /> <br /> Notification<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> |An instance of a message delivered to one or more recipients. A '''Notification''' activity sends a message to a user, both the<br /> recipients and the content that needs to be specified. Notification activities furthermore allow flow rulesets to be applied in<br /> order to notify users of events that occur during the workflow.<br /> <br /> A '''Notification''' provides often through technology a means of delivering a message to a set of recipients. One need to specify<br /> the recipients and then parameterize the subject and message that are sent.<br /> <br /> The '''Notification''' task allows you to send different types of notifications to the users of the application.<br /> |-<br /> |<br /> |[[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Mapping-01.png | 30px]]<br /> Mapping<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> |'''Mapping''' activities includes identifying, defining and plotting the involved business, information and data objects within the<br /> activities. This allows to identify possible grouping of common business, information and data objects and their associated<br /> rules (e.g. rulesets), enabling the change of complex objects and views into more simple views.<br /> <br /> A '''Mapping''' activity can be used to transform complex objects into more simple views (e.g. map data from data objects in the<br /> specific process context making it more simple data). Rules set can be used as a transform in a mapping activity. To make the<br /> mapping activity work, the mappings between the business, information and data objects in the process context needs to be<br /> defined.<br /> |-<br /> |<br /> | [[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Reporting-01.png | 30px]]<br /> Reporting<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> |'''Reporting''' is the exposure, description and portrayment of specific tasks, services and the associated information and data. The information and data objects/source can bind with the reporting activity the process components to the specific cockpits,<br /> dashboards or scorecards.<br /> <br /> To illustrate and express what is happening, or what has already happened, includes timely collection, analysis and then reporting of the information within the process. Depending if it is real time reporting or after the fact reporting, the input mapping needs to be specified.<br /> <br /> A '''Reporting''' activity is used to collect data and information in order to perform analytics on this data. The reporting activity<br /> references a reporting data source and indicates where in the process data is gathered for reporting. An input mapping<br /> needs to be defined for the reporting activity to specify which data from the process context is collected by the reporting<br /> activity.<br /> |-<br /> |<br /> |icon<br /> <br /> Business Object<br /> <br /> icon<br /> <br /> Collection of <br /> <br /> Business objects<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> |A '''Business Object''' is the term used to express real-world objects like people, employee, products or a sales order, customer and revenue. Business Objects used for example in business, process and service mapping and furthermore used in application<br /> implementations where they are used as a patented semantic layer that shields users from the complexities of information<br /> table names and data relationships.<br /> <br /> Below is a list of the different kinds of Business Objects that are commonly used in business modeling, process mapping and service mapping as well as in application and/or architectural mapping (e.g. business architecture, application architecture<br /> and solution architecture):<br /> <br /> • '''Business Object''' - Represents real-world objects like people, employee, products or a sales order, customer and revenue.<br /> <br /> • '''Collection of Business Objects''' - Represents a collection of real-world objects, e.g. a employee roles.<br /> <br /> • '''Business Input''' - Is an external input for the real-world objects. A kind of input parameter<br /> <br /> • '''Business Output''' - Is the real-world result of the entire process and or service flow. A kind of output parameter.<br /> <br /> • '''Business Store''' - Is a place where the real-world objects are stored.<br /> |-<br /> |<br /> |icon<br /> Information Object<br /> <br /> Collection of<br /> <br /> Information Objects<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> |An '''Information Object''' is used to specify information about real-world objects (like people, employees, products or a sales order, etc.), and is therefore a digital representation of an existing entity within an Information System (e.g. Oracle ERP or SAP<br /> ERP). It encompasses both the business information (in the form of functions and methods) and the application information (in the form of attributes) of the entity. Information Objects can be found and therefore modeled in business functions, business services and business processes.<br /> <br /> Below is a list of the different kinds of Information Objects used in business modeling, process mapping and service mapping as well as in application and/or architectural mapping (e.g. business architecture, information architecture, application architecture and solution architecture):<br /> <br /> • '''Information Object''' - Represents a container of information within the flow of the process and or service, such as business<br /> documents, e-mails, or letters.<br /> <br /> &lt;nowiki&gt; &lt;/nowiki&gt;• '''Collection of Information Objects''' - Represents a collection of information (e.g. a list of order items).<br /> <br /> • '''Information Input''' - Is an external information input for the entire process. A kind of input parameter.<br /> <br /> • '''Information Output''' - Is the information output/result of the entire process. A kind of output parameter.<br /> <br /> • '''Information Store''' - Is a place where the information can be read or written (e.g. knowledge management or a filing cabinet). It persists beyond the lifetime of the process instance.<br /> |-<br /> |<br /> |icon<br /> Data Object<br /> <br /> icon<br /> <br /> Collection of <br /> <br /> Data objects<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> |A Data Object is a logical cluster of all tables in the data set that have one or more columns containing data related to the same business entity. Data objects are not maps, but instead represent an object view of related Information Objects and they represent Business Objects.<br /> <br /> Below is a list of the different kinds of Data Objects used in process mapping and service mapping as well as in application<br /> and/or architectural mapping (e.g. information architecture, application architecture, solution architecture and data architecture):<br /> <br /> • '''Data Object''' - Represents a container/logical cluster of all tables in the data set that have one or more columns containing data related to the same data entity, such as business documents, e-mails, or letters.<br /> <br /> • '''Collection of Data Objects''' - Represents a collection of data tables/columns containing data related to the same data entity (e.g. a list of order items).<br /> <br /> • '''Data Input''' - Is an external data input for the entire process. A kind of input parameter.<br /> <br /> • '''Data Output''' - Is the data result of the entire process. A kind of output parameter.<br /> <br /> • '''Data Store''' - Is a place where the process can read or write data (e.g. a database or a filing cabinet). It persists beyond the lifetime of the process instance.<br /> |-<br /> |None<br /> |None<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |No special task type is indicated.<br /> |-<br /> |icon<br /> User<br /> |icon<br /> User<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''User Task''' is a typical “workflow” task where a human performer performs the task with the assistance of a software application<br /> and is scheduled through a task list manager of some sort.<br /> |-<br /> |icon<br /> Manual<br /> |icon<br /> Manual Task<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Manual Task''' is a task that is expected to be performed without the aid of any business process execution engine or any<br /> application.<br /> |-<br /> |<br /> |icon<br /> Automated Task<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> |An '''Automated Task''' is an activity that is automated through either a business process execution engine or any application<br /> (e.g. using application features and/or functions to enable the application task).<br /> |-<br /> |icon<br /> Service<br /> |<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Service Task''' is a task that uses some sort of service which could be a web service or an automated application.<br /> |-<br /> |<br /> |icon<br /> Manual Service<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> |A '''Manual Service''' is when the service is performed by a human.<br /> |-<br /> |<br /> |icon<br /> <br /> Automated Service<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> |An '''Automated Service''' can be either an application service, data service, platform service, infrastructure service or a web<br /> service.<br /> |-<br /> |icon<br /> <br /> Send<br /> |icon<br /> <br /> Send<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Send Task''' is a simple task that is designed to send a message to an external participant (relative to the process).<br /> |-<br /> |icon<br /> <br /> Receive<br /> |icon<br /> <br /> Receive<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Receive Tas'''k is a simple task that is designed to wait for a message to arrive from an external participant (relative to the<br /> process).<br /> |-<br /> |icon<br /> <br /> Script<br /> |icon<br /> <br /> Script<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Script Task''' is executed by a business process engine. The modeler or implementer defines a script in a language that the<br /> engine can interpret, and when the task is ready to start, the engine will execute the script. When the script is completed, the<br /> task will also be completed.<br /> |-<br /> |icon<br /> <br /> Business Rule<br /> |icon<br /> <br /> Business Rule<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Business Rule Task''' provides a mechanism for the process to provide input to a business rules engine, and to get the output<br /> of calculations that the business rules engine might provide. The input/output specification of the task will allow the process<br /> to send data to and receive data from the business rules engine.<br /> |-<br /> |<br /> |icon<br /> <br /> Ruleset<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> <br /> [[ Image:Logo ibm.png | 100px]] <br /> <br /> IBM WebSphere<br /> <br /> [[ Image:Microsoft.png | 100px]] <br /> <br /> Microsoft .NET<br /> |A '''Ruleset''' is a collection (and thereby a grouping) of rules. They are either grouped based on common related rules, decisions tables or the need to govern a specific set or behavior of tasks. Grouping such rulesets allows for sharing of rules and execution by a rules engine.<br /> <br /> A '''Ruleset''' is a logical collection of rules. A ruleset helps you group business rules that govern a specific function. A ruleset<br /> consists of: If-Then Rules and Decision Tables.<br /> <br /> A '''Ruleset''' is a container that includes definitions for a group of related rules and decision tables. A ruleset provides a unit of<br /> execution for rules and for Decision Tables. In addition, rulesets provide a unit of sharing for rules; rules belong to a ruleset.<br /> <br /> A '''Ruleset''' is a set of rules and rule artifacts that can be executed by the engine.<br /> <br /> A '''Ruleset''' contains a collection of rule classes along with the semantics for forward-chaining execution of those rules. A Ruleset<br /> can be executed directly in code or by using the Policy Activity activity<br /> |-<br /> |<br /> |icon<br /> <br /> Decision Table<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> <br /> [[ Image:Logo ibm.png | 100px]] <br /> <br /> IBM WebSphere<br /> <br /> [[ Image:Microsoft.png | 100px]] <br /> <br /> Microsoft .NET<br /> |A '''Decision Table''' defines decisions based on a number of given conditions and actions. Decision tables allow to work from<br /> the same information, and are therefore a precise way to model complicated logics and associations.<br /> <br /> A '''Decision Table''' can either be a tabular representation of related rules or a precise yet compact way to map complicated logic. Decision tables, like flowcharts and if-then-else and switch-case statements, associate conditions with actions to perform, but in many cases do so in a more elegant way.<br /> <br /> An example of using a '''Decision Table''' is an activity to evaluate based on the region and the total amount of the order, whether<br /> or not the approval of a supervisor is required or not. Would be good to have this as a reusable task instead of embedded in<br /> the gateway. The gateway can then just do the branching. Could include a link to a spreadsheet for example.<br /> <br /> '''Decision Tables''' provide an alternative way of viewing and managing large sets of symmetric business rules. A decision table<br /> contains condition columns and action columns.<br /> <br /> '''Decision Tables''' are a simple and clean method of representing large sets of business rules<br /> |-<br /> |<br /> |icon <br /> <br /> Rule Script<br /> |<br /> <br /> [[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> <br /> [[ Image:Logo ibm.png | 100px]] <br /> <br /> IBM WebSphere<br /> |'''Rule Flows''' are comprised of linked tasks that contain the instructions for which rules to execute and in what order. The rules are organized into tasks, and the rule flow specifies how tasks are chained together; how, when, and under what conditions<br /> they are executed. When you are dealing with many large rulesets, managing the order in which rules are evaluated can become complex. Rule flows allows you to specify the order in which rulesets are to be evaluated. It does so by providing you with a flow chart. Use this chart to define which rule sets should be evaluated in sequence, and which ones in parallel, and to specify conditions under which rule sets should be evaluated. The reuse of rules components and their natural relations like activity association are an important aspect of rule modelling principles. This allows for rule modelling consistency between the different rule artifacts from the rule flows, rule scripts, rulesets, flow rulesets, rules and decision tables.<br /> <br /> In order to do advanced project or business area rule modelling, it might be necessary to categorize some of the rules into<br /> main and sub rules. A project can contain many rule flows, one of which must be identified as the main rule flow of the project or area. Additional rule flows could then be added and modelled from the main rule flow. Other rule flows are then included through sub flow tasks.<br /> <br /> A '''Rule Flow''' is a sequence of activities for evaluating business rules. The order of the execution of the rules is diagrammatically<br /> represented in the form of a flow chart. It is a reusable entity within a flow ruleset, and is based on activities associated with artifacts such as rule scripts, rule flows, rulesets, flow rulesets, rules and decision tables.<br /> <br /> Multiple rulesets can be executed in order. This is called a '''Rule Flow'''. The ruleset stack determines the order. The order can be manipulated by rule actions that push and pop rulesets on the stack. In rulesets, the priority of rules applies to specify the order of firing of the rules in the ruleset. Rulesets also provide an effective date specification that identifies that the ruleset is always active, or that the ruleset is restricted based on a time and date range, or a starting or ending time and date.<br /> <br /> A '''Rule Flow''' defines the flow of execution of the rules. The rules are organized into tasks and the ruleflow specifies how tasks<br /> are chained together; how, when, and under what conditions they are executed.<br /> |-<br /> |<br /> |icon<br /> <br /> Rule Script<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> [[ Image:Microsoft.png | 100px]] <br /> <br /> Microsoft .NET<br /> |A '''Rule Script''' allows generating a rule in a scripting environment. This is done through the connection of other activities and the rules that govern these relations, and the actions between them. Rule scripts can furthermore be used with script types, and thereby automated test rules (e.g. configurable, programmed, query and event-based network alerts). The link between rule scripts and the mentioned script type could be used as template–based query that can be run against backend tables or database views.<br /> <br /> A '''Rule Script''' is a reusable artifact within a flow ruleset and is a sequence of actions. It is associated with other activities in a flow ruleset, and is triggered when the conditions listed in the preceding activities are satisfied.<br /> <br /> A rule script can contain any of the following action types: Assign Action, Assert Action, Evaluate Decision, Table Action,<br /> Execute Action, Execute Ruleset Action, Execute Rule Action, For Each Action, If Else, If Action, While Action, Retract Action, Break and Continue Actions.<br /> <br /> The '''Rule Script''' allows to generate a rule from a scripting environment.<br /> |}<br /> [[Category:Objects]]<br /> {{DISPLAYTITLE:X-BPMN Notations2}}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=Objects:BPMN_2.0_versus_eXtended_BPMN_(X-BPMN)&diff=914 2015-07-20T13:57:18Z

<p>Fbajohr: </p> <hr /> <div>'''Business Process Representation'''Business process modelling is the discipline of graphically representing a process into a readable diagram. The Business Process Modelling Notation (BPMN) is a graphical notation that depicts the steps in an end to end flow of a business process. The notation has been specifically designed to coordinate the sequence of processes and the messages that flow between different process participants in a related set of activities. BPMN is a vendor neutral, world-wide accepted standard managed by the Object Management Group (OMG) that provides a common way to model business processes. It offers both the simplicity and complexity required to model business processes for both the business audience as well as the technical audience. The LEAD Process Mapping standards is released as a part of the LEADing Practices and will be subject to continuous improvement and development.<br /> <br /> &lt;br/&gt;<br /> <br /> '''History of Business Process Modelling Notations'''<br /> <br /> • March 2001: BPMI members began discussing the idea of creating a notation to go along with the executable BPML. <br /> <br /> • August 2004: BPMN 1.0 specification was released to the public.<br /> • Now maintained by the Object Management Group (OMG). <br /> <br /> • January 2011: BPMN 2.0 specification was released to the public. <br /> <br /> &lt;br/&gt;<br /> <br /> '''LEADing Practice''' then further developed upon the BPMN 2.0 specification to include linkage to: <br /> <br /> • Business Competencies (January 2011). <br /> <br /> • Service Mapping (January 2011). <br /> <br /> • Interaction Models (March 2011). <br /> <br /> • RACI Mapping (May 2011). <br /> <br /> • Value Mapping (November 2011). <br /> <br /> • SAP Netweaver connection (January 2012). <br /> <br /> • SAP Solution Manager connection (February 2012). <br /> <br /> • Incorporation of LEAD X-BPMN principles into iGrafx (November 2012).<br /> <br /> BPMN 2.0 versus eXtended BPMN (X-BPMN) Process Modelling<br /> <br /> {| class=&quot;wikitable&quot; <br /> |+ <br /> |- <br /> ! BPMN 2.0 !! X-BPMN !! Source !! scope=&quot;col&quot; width=&quot;75%&quot; | Description <br /> <br /> |- <br /> ||| [[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Rule-01.png | 30px ]] <br /> Rule <br /> <br /> || [[ Image:Leadin.png | 100px]] <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> <br /> [[ Image:Logo ibm.png | 100px]] <br /> <br /> IBM WebSphere<br /> <br /> <br /> [[ Image:Microsoft.png | 100px]] <br /> <br /> Microsoft .NET <br /> || A '''Rule''' is a statement describing a business policy or decision procedure. Some programming languages run business rules<br /> together in very complex algorithms. In business process analysis, each rule is usually stated independently, in the general<br /> format of: If A and B, Then C.<br /> <br /> Workflow tools and detailed process diagrams both depend on business rules to specify how decisions are made. We generally associate business rules with activities. A decision table is adequate to show what happens if A or B happens, but dozens<br /> or even hundreds of business rules may need to be defined to clarify if A or B should happen. Training programs, job aids,<br /> software systems, and knowledge management systems aim to document business rules either to automate the decision<br /> process or to and make the rules available to other decision makers.<br /> <br /> A '''Rule''' is a set of conditions and associated actions that are performed when the conditions are satisfied. Rules can be written<br /> in two forms: as If and Then-statements, and as Decision Tables.<br /> <br /> Business '''Rules''' are statements that describe business policies or describe key business decisions.<br /> <br /> An action '''Rule''' is made of a condition part and of an action part. The first part of the rule defines the condition in which the<br /> rule applies. The second part of the rule defines the action to take if the condition of the rule is true.<br /> <br /> A '''Rule''' defines a condition with an associated set of actions to perform. Rules can be related to:<br /> <br /> • Active: Gets or sets a value that indicates whether the Rule should be evaluated.<br /> <br /> • Condition: Gets or sets a RuleCondition for the Rule to evaluate.<br /> <br /> • Description: Gets or sets a description of the Rule.<br /> <br /> • ElseActions: Gets a collection of RuleAction classes to perform in the ELSE case.<br /> <br /> • Name: Gets or sets the name of the Rule.<br /> <br /> • Priority: Gets or sets a value that indicates the order in which a Rule should be run.<br /> <br /> • Reevaluation: Behavior gets or sets a value indicating whether a Rule can be reevaluated.<br /> <br /> • ThenActions: Gets a collection of RuleAction classes to perform in the THEN case.<br /> |-<br /> |<br /> | [[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Flow_Ruleset-01.png | 30px]] <br /> Flow Ruleset <br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> | A '''Flow Ruleset''' is a collection (and thereby grouping) of rules that apply to a flow. These flow rulesets are either grouped<br /> based on common related rules in the flow, decisions tables, or the need to govern a specific set or behavior of tasks in the<br /> flow. Grouping such flow rulesets allows for sharing of rules and execution, by a rule engine throughout the entire flow. As<br /> well as the relation to the reuse of such rulsets in other flows, starting from the main flow where the ruleset are applied.<br /> <br /> A '''Flow Ruleset''' is a ruleset that allows you to group business rules that need to be executed as in a flow chart. It always has<br /> one flow, designated as main flow, besides possibly many other rule flows. The execution of the Flow Ruleset starts with the<br /> main flow. A Flow Ruleset consists of: Aliases, Definition, Rule Flow, Rule Scripts, If-Then Rules and Decision Tables.<br /> |-<br /> |<br /> |[[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Notification-01.png | 30px]]<br /> <br /> Notification<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> |An instance of a message delivered to one or more recipients. A '''Notification''' activity sends a message to a user, both the<br /> recipients and the content that needs to be specified. Notification activities furthermore allow flow rulesets to be applied in<br /> order to notify users of events that occur during the workflow.<br /> <br /> A '''Notification''' provides often through technology a means of delivering a message to a set of recipients. One need to specify<br /> the recipients and then parameterize the subject and message that are sent.<br /> <br /> The '''Notification''' task allows you to send different types of notifications to the users of the application.<br /> |-<br /> |<br /> |[[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Mapping-01.png | 30px]]<br /> Mapping<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> |'''Mapping''' activities includes identifying, defining and plotting the involved business, information and data objects within the<br /> activities. This allows to identify possible grouping of common business, information and data objects and their associated<br /> rules (e.g. rulesets), enabling the change of complex objects and views into more simple views.<br /> <br /> A '''Mapping''' activity can be used to transform complex objects into more simple views (e.g. map data from data objects in the<br /> specific process context making it more simple data). Rules set can be used as a transform in a mapping activity. To make the<br /> mapping activity work, the mappings between the business, information and data objects in the process context needs to be<br /> defined.<br /> |-<br /> |<br /> | [[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Reporting-01.png | 30px]]<br /> Reporting<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> |'''Reporting''' is the exposure, description and portrayment of specific tasks, services and the associated information and data. The information and data objects/source can bind with the reporting activity the process components to the specific cockpits,<br /> dashboards or scorecards.<br /> <br /> To illustrate and express what is happening, or what has already happened, includes timely collection, analysis and then reporting of the information within the process. Depending if it is real time reporting or after the fact reporting, the input mapping needs to be specified.<br /> <br /> A '''Reporting''' activity is used to collect data and information in order to perform analytics on this data. The reporting activity<br /> references a reporting data source and indicates where in the process data is gathered for reporting. An input mapping<br /> needs to be defined for the reporting activity to specify which data from the process context is collected by the reporting<br /> activity.<br /> |-<br /> |<br /> |icon<br /> <br /> Business Object<br /> <br /> icon<br /> <br /> Collection of <br /> <br /> Business objects<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> |A '''Business Object''' is the term used to express real-world objects like people, employee, products or a sales order, customer and revenue. Business Objects used for example in business, process and service mapping and furthermore used in application<br /> implementations where they are used as a patented semantic layer that shields users from the complexities of information<br /> table names and data relationships.<br /> <br /> Below is a list of the different kinds of Business Objects that are commonly used in business modeling, process mapping and service mapping as well as in application and/or architectural mapping (e.g. business architecture, application architecture<br /> and solution architecture):<br /> <br /> • '''Business Object''' - Represents real-world objects like people, employee, products or a sales order, customer and revenue.<br /> <br /> • '''Collection of Business Objects''' - Represents a collection of real-world objects, e.g. a employee roles.<br /> <br /> • '''Business Input''' - Is an external input for the real-world objects. A kind of input parameter<br /> <br /> • '''Business Output''' - Is the real-world result of the entire process and or service flow. A kind of output parameter.<br /> <br /> • '''Business Store''' - Is a place where the real-world objects are stored.<br /> |-<br /> |<br /> |icon<br /> Information Object<br /> <br /> Collection of<br /> <br /> Information Objects<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> |An '''Information Object''' is used to specify information about real-world objects (like people, employees, products or a sales order, etc.), and is therefore a digital representation of an existing entity within an Information System (e.g. Oracle ERP or SAP<br /> ERP). It encompasses both the business information (in the form of functions and methods) and the application information (in the form of attributes) of the entity. Information Objects can be found and therefore modeled in business functions, business services and business processes.<br /> <br /> Below is a list of the different kinds of Information Objects used in business modeling, process mapping and service mapping as well as in application and/or architectural mapping (e.g. business architecture, information architecture, application architecture and solution architecture):<br /> <br /> • '''Information Object''' - Represents a container of information within the flow of the process and or service, such as business<br /> documents, e-mails, or letters.<br /> <br /> &lt;nowiki&gt; &lt;/nowiki&gt;• '''Collection of Information Objects''' - Represents a collection of information (e.g. a list of order items).<br /> <br /> • '''Information Input''' - Is an external information input for the entire process. A kind of input parameter.<br /> <br /> • '''Information Output''' - Is the information output/result of the entire process. A kind of output parameter.<br /> <br /> • '''Information Store''' - Is a place where the information can be read or written (e.g. knowledge management or a filing cabinet). It persists beyond the lifetime of the process instance.<br /> |-<br /> |<br /> |icon<br /> Data Object<br /> <br /> icon<br /> <br /> Collection of <br /> <br /> Data objects<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> |A Data Object is a logical cluster of all tables in the data set that have one or more columns containing data related to the same business entity. Data objects are not maps, but instead represent an object view of related Information Objects and they represent Business Objects.<br /> <br /> Below is a list of the different kinds of Data Objects used in process mapping and service mapping as well as in application<br /> and/or architectural mapping (e.g. information architecture, application architecture, solution architecture and data architecture):<br /> <br /> • '''Data Object''' - Represents a container/logical cluster of all tables in the data set that have one or more columns containing data related to the same data entity, such as business documents, e-mails, or letters.<br /> <br /> • '''Collection of Data Objects''' - Represents a collection of data tables/columns containing data related to the same data entity (e.g. a list of order items).<br /> <br /> • '''Data Input''' - Is an external data input for the entire process. A kind of input parameter.<br /> <br /> • '''Data Output''' - Is the data result of the entire process. A kind of output parameter.<br /> <br /> • '''Data Store''' - Is a place where the process can read or write data (e.g. a database or a filing cabinet). It persists beyond the lifetime of the process instance.<br /> |-<br /> |None<br /> |None<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |No special task type is indicated.<br /> |-<br /> |icon<br /> User<br /> |icon<br /> User<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''User Task''' is a typical “workflow” task where a human performer performs the task with the assistance of a software application<br /> and is scheduled through a task list manager of some sort.<br /> |-<br /> |icon<br /> Manual<br /> |icon<br /> Manual Task<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Manual Task''' is a task that is expected to be performed without the aid of any business process execution engine or any<br /> application.<br /> |-<br /> |<br /> |icon<br /> Automated Task<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> |An '''Automated Task''' is an activity that is automated through either a business process execution engine or any application<br /> (e.g. using application features and/or functions to enable the application task).<br /> |-<br /> |icon<br /> Service<br /> |<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Service Task''' is a task that uses some sort of service which could be a web service or an automated application.<br /> |-<br /> |<br /> |icon<br /> Manual Service<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> |A '''Manual Service''' is when the service is performed by a human.<br /> |-<br /> |<br /> |icon<br /> <br /> Automated Service<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> |An '''Automated Service''' can be either an application service, data service, platform service, infrastructure service or a web<br /> service.<br /> |-<br /> |icon<br /> <br /> Send<br /> |icon<br /> <br /> Send<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Send Task''' is a simple task that is designed to send a message to an external participant (relative to the process).<br /> |-<br /> |icon<br /> <br /> Receive<br /> |icon<br /> <br /> Receive<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Receive Tas'''k is a simple task that is designed to wait for a message to arrive from an external participant (relative to the<br /> process).<br /> |-<br /> |icon<br /> <br /> Script<br /> |icon<br /> <br /> Script<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Script Task''' is executed by a business process engine. The modeler or implementer defines a script in a language that the<br /> engine can interpret, and when the task is ready to start, the engine will execute the script. When the script is completed, the<br /> task will also be completed.<br /> |-<br /> |icon<br /> <br /> Business Rule<br /> |icon<br /> <br /> Business Rule<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Business Rule Task''' provides a mechanism for the process to provide input to a business rules engine, and to get the output<br /> of calculations that the business rules engine might provide. The input/output specification of the task will allow the process<br /> to send data to and receive data from the business rules engine.<br /> |-<br /> |<br /> |icon<br /> <br /> Ruleset<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> <br /> [[ Image:Logo ibm.png | 100px]] <br /> <br /> IBM WebSphere<br /> <br /> [[ Image:Microsoft.png | 100px]] <br /> <br /> Microsoft .NET<br /> |A '''Ruleset''' is a collection (and thereby a grouping) of rules. They are either grouped based on common related rules, decisions tables or the need to govern a specific set or behavior of tasks. Grouping such rulesets allows for sharing of rules and execution by a rules engine.<br /> <br /> A '''Ruleset''' is a logical collection of rules. A ruleset helps you group business rules that govern a specific function. A ruleset<br /> consists of: If-Then Rules and Decision Tables.<br /> <br /> A '''Ruleset''' is a container that includes definitions for a group of related rules and decision tables. A ruleset provides a unit of<br /> execution for rules and for Decision Tables. In addition, rulesets provide a unit of sharing for rules; rules belong to a ruleset.<br /> <br /> A '''Ruleset''' is a set of rules and rule artifacts that can be executed by the engine.<br /> <br /> A '''Ruleset''' contains a collection of rule classes along with the semantics for forward-chaining execution of those rules. A Ruleset<br /> can be executed directly in code or by using the Policy Activity activity<br /> |-<br /> |<br /> |icon<br /> <br /> Decision Table<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> <br /> [[ Image:Logo ibm.png | 100px]] <br /> <br /> IBM WebSphere<br /> <br /> [[ Image:Microsoft.png | 100px]] <br /> <br /> Microsoft .NET<br /> |A '''Decision Table''' defines decisions based on a number of given conditions and actions. Decision tables allow to work from<br /> the same information, and are therefore a precise way to model complicated logics and associations.<br /> <br /> A '''Decision Table''' can either be a tabular representation of related rules or a precise yet compact way to map complicated logic. Decision tables, like flowcharts and if-then-else and switch-case statements, associate conditions with actions to perform, but in many cases do so in a more elegant way.<br /> <br /> An example of using a '''Decision Table''' is an activity to evaluate based on the region and the total amount of the order, whether<br /> or not the approval of a supervisor is required or not. Would be good to have this as a reusable task instead of embedded in<br /> the gateway. The gateway can then just do the branching. Could include a link to a spreadsheet for example.<br /> <br /> '''Decision Tables''' provide an alternative way of viewing and managing large sets of symmetric business rules. A decision table<br /> contains condition columns and action columns.<br /> <br /> '''Decision Tables''' are a simple and clean method of representing large sets of business rules<br /> |-<br /> |<br /> |icon <br /> <br /> Rule Script<br /> |<br /> <br /> [[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> <br /> [[ Image:Logo ibm.png | 100px]] <br /> <br /> IBM WebSphere<br /> |'''Rule Flows''' are comprised of linked tasks that contain the instructions for which rules to execute and in what order. The rules are organized into tasks, and the rule flow specifies how tasks are chained together; how, when, and under what conditions<br /> they are executed. When you are dealing with many large rulesets, managing the order in which rules are evaluated can become complex. Rule flows allows you to specify the order in which rulesets are to be evaluated. It does so by providing you with a flow chart. Use this chart to define which rule sets should be evaluated in sequence, and which ones in parallel, and to specify conditions under which rule sets should be evaluated. The reuse of rules components and their natural relations like activity association are an important aspect of rule modelling principles. This allows for rule modelling consistency between the different rule artifacts from the rule flows, rule scripts, rulesets, flow rulesets, rules and decision tables.<br /> <br /> In order to do advanced project or business area rule modelling, it might be necessary to categorize some of the rules into<br /> main and sub rules. A project can contain many rule flows, one of which must be identified as the main rule flow of the project or area. Additional rule flows could then be added and modelled from the main rule flow. Other rule flows are then included through sub flow tasks.<br /> <br /> A '''Rule Flow''' is a sequence of activities for evaluating business rules. The order of the execution of the rules is diagrammatically<br /> represented in the form of a flow chart. It is a reusable entity within a flow ruleset, and is based on activities associated with artifacts such as rule scripts, rule flows, rulesets, flow rulesets, rules and decision tables.<br /> <br /> Multiple rulesets can be executed in order. This is called a '''Rule Flow'''. The ruleset stack determines the order. The order can be manipulated by rule actions that push and pop rulesets on the stack. In rulesets, the priority of rules applies to specify the order of firing of the rules in the ruleset. Rulesets also provide an effective date specification that identifies that the ruleset is always active, or that the ruleset is restricted based on a time and date range, or a starting or ending time and date.<br /> <br /> A '''Rule Flow''' defines the flow of execution of the rules. The rules are organized into tasks and the ruleflow specifies how tasks<br /> are chained together; how, when, and under what conditions they are executed.<br /> |-<br /> |<br /> |icon<br /> <br /> Rule Script<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> [[ Image:Microsoft.png | 100px]] <br /> <br /> Microsoft .NET<br /> |A '''Rule Script''' allows generating a rule in a scripting environment. This is done through the connection of other activities and the rules that govern these relations, and the actions between them. Rule scripts can furthermore be used with script types, and thereby automated test rules (e.g. configurable, programmed, query and event-based network alerts). The link between rule scripts and the mentioned script type could be used as template–based query that can be run against backend tables or database views.<br /> <br /> A '''Rule Script''' is a reusable artifact within a flow ruleset and is a sequence of actions. It is associated with other activities in a flow ruleset, and is triggered when the conditions listed in the preceding activities are satisfied.<br /> <br /> A rule script can contain any of the following action types: Assign Action, Assert Action, Evaluate Decision, Table Action,<br /> Execute Action, Execute Ruleset Action, Execute Rule Action, For Each Action, If Else, If Action, While Action, Retract Action, Break and Continue Actions.<br /> <br /> The '''Rule Script''' allows to generate a rule from a scripting environment.<br /> |}<br /> [[Category:Objects]]<br /> {{DISPLAYTITLE:X-BPMN Notations}}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=Objects:BPMN_2.0_versus_eXtended_BPMN_(X-BPMN)&diff=913 2015-07-20T13:36:19Z

<p>Fbajohr: </p> <hr /> <div>'''Business Process Representation'''Business process modelling is the discipline of graphically representing a process into a readable diagram. The Business Process Modelling Notation (BPMN) is a graphical notation that depicts the steps in an end to end flow of a business process. The notation has been specifically designed to coordinate the sequence of processes and the messages that flow between different process participants in a related set of activities. BPMN is a vendor neutral, world-wide accepted standard managed by the Object Management Group (OMG) that provides a common way to model business processes. It offers both the simplicity and complexity required to model business processes for both the business audience as well as the technical audience. The LEAD Process Mapping standards is released as a part of the LEADing Practices and will be subject to continuous improvement and development.<br /> <br /> &lt;br/&gt;<br /> <br /> '''History of Business Process Modelling Notations'''<br /> <br /> • March 2001: BPMI members began discussing the idea of creating a notation to go along with the executable BPML. <br /> <br /> • August 2004: BPMN 1.0 specification was released to the public.<br /> • Now maintained by the Object Management Group (OMG). <br /> <br /> • January 2011: BPMN 2.0 specification was released to the public. <br /> <br /> &lt;br/&gt;<br /> <br /> '''LEADing Practice''' then further developed upon the BPMN 2.0 specification to include linkage to: <br /> <br /> • Business Competencies (January 2011). <br /> <br /> • Service Mapping (January 2011). <br /> <br /> • Interaction Models (March 2011). <br /> <br /> • RACI Mapping (May 2011). <br /> <br /> • Value Mapping (November 2011). <br /> <br /> • SAP Netweaver connection (January 2012). <br /> <br /> • SAP Solution Manager connection (February 2012). <br /> <br /> • Incorporation of LEAD X-BPMN principles into iGrafx (November 2012).<br /> <br /> BPMN 2.0 versus eXtended BPMN (X-BPMN) Process Modelling<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;margin: 1em auto 1em auto;&quot;<br /> |+<br /> |- <br /> ! BPMN 2.0 !! X-BPMN !! Source !! scope=&quot;col&quot; width=&quot;75%&quot; | Description <br /> <br /> |- <br /> ||| [[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Rule-01.png | 30px ]] <br /> Rule <br /> <br /> || [[ Image:Leadin.png | 100px]] <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> <br /> [[ Image:Logo ibm.png | 100px]] <br /> <br /> IBM WebSphere<br /> <br /> <br /> [[ Image:Microsoft.png | 100px]] <br /> <br /> Microsoft .NET <br /> || A '''Rule''' is a statement describing a business policy or decision procedure. Some programming languages run business rules<br /> together in very complex algorithms. In business process analysis, each rule is usually stated independently, in the general<br /> format of: If A and B, Then C.<br /> <br /> Workflow tools and detailed process diagrams both depend on business rules to specify how decisions are made. We generally associate business rules with activities. A decision table is adequate to show what happens if A or B happens, but dozens<br /> or even hundreds of business rules may need to be defined to clarify if A or B should happen. Training programs, job aids,<br /> software systems, and knowledge management systems aim to document business rules either to automate the decision<br /> process or to and make the rules available to other decision makers.<br /> <br /> A '''Rule''' is a set of conditions and associated actions that are performed when the conditions are satisfied. Rules can be written<br /> in two forms: as If and Then-statements, and as Decision Tables.<br /> <br /> Business '''Rules''' are statements that describe business policies or describe key business decisions.<br /> <br /> An action '''Rule''' is made of a condition part and of an action part. The first part of the rule defines the condition in which the<br /> rule applies. The second part of the rule defines the action to take if the condition of the rule is true.<br /> <br /> A '''Rule''' defines a condition with an associated set of actions to perform. Rules can be related to:<br /> <br /> • Active: Gets or sets a value that indicates whether the Rule should be evaluated.<br /> <br /> • Condition: Gets or sets a RuleCondition for the Rule to evaluate.<br /> <br /> • Description: Gets or sets a description of the Rule.<br /> <br /> • ElseActions: Gets a collection of RuleAction classes to perform in the ELSE case.<br /> <br /> • Name: Gets or sets the name of the Rule.<br /> <br /> • Priority: Gets or sets a value that indicates the order in which a Rule should be run.<br /> <br /> • Reevaluation: Behavior gets or sets a value indicating whether a Rule can be reevaluated.<br /> <br /> • ThenActions: Gets a collection of RuleAction classes to perform in the THEN case.<br /> |-<br /> |<br /> | [[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Flow_Ruleset-01.png | 30px]] <br /> Flow Ruleset <br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> | A '''Flow Ruleset''' is a collection (and thereby grouping) of rules that apply to a flow. These flow rulesets are either grouped<br /> based on common related rules in the flow, decisions tables, or the need to govern a specific set or behavior of tasks in the<br /> flow. Grouping such flow rulesets allows for sharing of rules and execution, by a rule engine throughout the entire flow. As<br /> well as the relation to the reuse of such rulsets in other flows, starting from the main flow where the ruleset are applied.<br /> <br /> A '''Flow Ruleset''' is a ruleset that allows you to group business rules that need to be executed as in a flow chart. It always has<br /> one flow, designated as main flow, besides possibly many other rule flows. The execution of the Flow Ruleset starts with the<br /> main flow. A Flow Ruleset consists of: Aliases, Definition, Rule Flow, Rule Scripts, If-Then Rules and Decision Tables.<br /> |-<br /> |<br /> |[[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Notification-01.png | 30px]]<br /> <br /> Notification<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> |An instance of a message delivered to one or more recipients. A '''Notification''' activity sends a message to a user, both the<br /> recipients and the content that needs to be specified. Notification activities furthermore allow flow rulesets to be applied in<br /> order to notify users of events that occur during the workflow.<br /> <br /> A '''Notification''' provides often through technology a means of delivering a message to a set of recipients. One need to specify<br /> the recipients and then parameterize the subject and message that are sent.<br /> <br /> The '''Notification''' task allows you to send different types of notifications to the users of the application.<br /> |-<br /> |<br /> |[[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Mapping-01.png | 30px]]<br /> Mapping<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> |'''Mapping''' activities includes identifying, defining and plotting the involved business, information and data objects within the<br /> activities. This allows to identify possible grouping of common business, information and data objects and their associated<br /> rules (e.g. rulesets), enabling the change of complex objects and views into more simple views.<br /> <br /> A '''Mapping''' activity can be used to transform complex objects into more simple views (e.g. map data from data objects in the<br /> specific process context making it more simple data). Rules set can be used as a transform in a mapping activity. To make the<br /> mapping activity work, the mappings between the business, information and data objects in the process context needs to be<br /> defined.<br /> |-<br /> |<br /> | [[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Reporting-01.png | 30px]]<br /> Reporting<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> |'''Reporting''' is the exposure, description and portrayment of specific tasks, services and the associated information and data. The information and data objects/source can bind with the reporting activity the process components to the specific cockpits,<br /> dashboards or scorecards.<br /> <br /> To illustrate and express what is happening, or what has already happened, includes timely collection, analysis and then reporting of the information within the process. Depending if it is real time reporting or after the fact reporting, the input mapping needs to be specified.<br /> <br /> A '''Reporting''' activity is used to collect data and information in order to perform analytics on this data. The reporting activity<br /> references a reporting data source and indicates where in the process data is gathered for reporting. An input mapping<br /> needs to be defined for the reporting activity to specify which data from the process context is collected by the reporting<br /> activity.<br /> |-<br /> |<br /> |icon<br /> <br /> Business Object<br /> <br /> icon<br /> <br /> Collection of <br /> <br /> Business objects<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> |A '''Business Object''' is the term used to express real-world objects like people, employee, products or a sales order, customer and revenue. Business Objects used for example in business, process and service mapping and furthermore used in application<br /> implementations where they are used as a patented semantic layer that shields users from the complexities of information<br /> table names and data relationships.<br /> <br /> Below is a list of the different kinds of Business Objects that are commonly used in business modeling, process mapping and service mapping as well as in application and/or architectural mapping (e.g. business architecture, application architecture<br /> and solution architecture):<br /> <br /> • '''Business Object''' - Represents real-world objects like people, employee, products or a sales order, customer and revenue.<br /> <br /> • '''Collection of Business Objects''' - Represents a collection of real-world objects, e.g. a employee roles.<br /> <br /> • '''Business Input''' - Is an external input for the real-world objects. A kind of input parameter<br /> <br /> • '''Business Output''' - Is the real-world result of the entire process and or service flow. A kind of output parameter.<br /> <br /> • '''Business Store''' - Is a place where the real-world objects are stored.<br /> |-<br /> |<br /> |icon<br /> Information Object<br /> <br /> Collection of<br /> <br /> Information Objects<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> |An '''Information Object''' is used to specify information about real-world objects (like people, employees, products or a sales order, etc.), and is therefore a digital representation of an existing entity within an Information System (e.g. Oracle ERP or SAP<br /> ERP). It encompasses both the business information (in the form of functions and methods) and the application information (in the form of attributes) of the entity. Information Objects can be found and therefore modeled in business functions, business services and business processes.<br /> <br /> Below is a list of the different kinds of Information Objects used in business modeling, process mapping and service mapping as well as in application and/or architectural mapping (e.g. business architecture, information architecture, application architecture and solution architecture):<br /> <br /> • '''Information Object''' - Represents a container of information within the flow of the process and or service, such as business<br /> documents, e-mails, or letters.<br /> <br /> &lt;nowiki&gt; &lt;/nowiki&gt;• '''Collection of Information Objects''' - Represents a collection of information (e.g. a list of order items).<br /> <br /> • '''Information Input''' - Is an external information input for the entire process. A kind of input parameter.<br /> <br /> • '''Information Output''' - Is the information output/result of the entire process. A kind of output parameter.<br /> <br /> • '''Information Store''' - Is a place where the information can be read or written (e.g. knowledge management or a filing cabinet). It persists beyond the lifetime of the process instance.<br /> |-<br /> |<br /> |icon<br /> Data Object<br /> <br /> icon<br /> <br /> Collection of <br /> <br /> Data objects<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> |A Data Object is a logical cluster of all tables in the data set that have one or more columns containing data related to the same business entity. Data objects are not maps, but instead represent an object view of related Information Objects and they represent Business Objects.<br /> <br /> Below is a list of the different kinds of Data Objects used in process mapping and service mapping as well as in application<br /> and/or architectural mapping (e.g. information architecture, application architecture, solution architecture and data architecture):<br /> <br /> • '''Data Object''' - Represents a container/logical cluster of all tables in the data set that have one or more columns containing data related to the same data entity, such as business documents, e-mails, or letters.<br /> <br /> • '''Collection of Data Objects''' - Represents a collection of data tables/columns containing data related to the same data entity (e.g. a list of order items).<br /> <br /> • '''Data Input''' - Is an external data input for the entire process. A kind of input parameter.<br /> <br /> • '''Data Output''' - Is the data result of the entire process. A kind of output parameter.<br /> <br /> • '''Data Store''' - Is a place where the process can read or write data (e.g. a database or a filing cabinet). It persists beyond the lifetime of the process instance.<br /> |-<br /> |None<br /> |None<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |No special task type is indicated.<br /> |-<br /> |icon<br /> User<br /> |icon<br /> User<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''User Task''' is a typical “workflow” task where a human performer performs the task with the assistance of a software application<br /> and is scheduled through a task list manager of some sort.<br /> |-<br /> |icon<br /> Manual<br /> |icon<br /> Manual Task<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Manual Task''' is a task that is expected to be performed without the aid of any business process execution engine or any<br /> application.<br /> |-<br /> |<br /> |icon<br /> Automated Task<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> |An '''Automated Task''' is an activity that is automated through either a business process execution engine or any application<br /> (e.g. using application features and/or functions to enable the application task).<br /> |-<br /> |icon<br /> Service<br /> |<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Service Task''' is a task that uses some sort of service which could be a web service or an automated application.<br /> |-<br /> |<br /> |icon<br /> Manual Service<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> |A '''Manual Service''' is when the service is performed by a human.<br /> |-<br /> |<br /> |icon<br /> <br /> Automated Service<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> |An '''Automated Service''' can be either an application service, data service, platform service, infrastructure service or a web<br /> service.<br /> |-<br /> |icon<br /> <br /> Send<br /> |icon<br /> <br /> Send<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Send Task''' is a simple task that is designed to send a message to an external participant (relative to the process).<br /> |-<br /> |icon<br /> <br /> Receive<br /> |icon<br /> <br /> Receive<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Receive Tas'''k is a simple task that is designed to wait for a message to arrive from an external participant (relative to the<br /> process).<br /> |-<br /> |icon<br /> <br /> Script<br /> |icon<br /> <br /> Script<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Script Task''' is executed by a business process engine. The modeler or implementer defines a script in a language that the<br /> engine can interpret, and when the task is ready to start, the engine will execute the script. When the script is completed, the<br /> task will also be completed.<br /> |-<br /> |icon<br /> <br /> Business Rule<br /> |icon<br /> <br /> Business Rule<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Business Rule Task''' provides a mechanism for the process to provide input to a business rules engine, and to get the output<br /> of calculations that the business rules engine might provide. The input/output specification of the task will allow the process<br /> to send data to and receive data from the business rules engine.<br /> |-<br /> |<br /> |icon<br /> <br /> Ruleset<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> <br /> [[ Image:Logo ibm.png | 100px]] <br /> <br /> IBM WebSphere<br /> <br /> [[ Image:Microsoft.png | 100px]] <br /> <br /> Microsoft .NET<br /> |A '''Ruleset''' is a collection (and thereby a grouping) of rules. They are either grouped based on common related rules, decisions tables or the need to govern a specific set or behavior of tasks. Grouping such rulesets allows for sharing of rules and execution by a rules engine.<br /> <br /> A '''Ruleset''' is a logical collection of rules. A ruleset helps you group business rules that govern a specific function. A ruleset<br /> consists of: If-Then Rules and Decision Tables.<br /> <br /> A '''Ruleset''' is a container that includes definitions for a group of related rules and decision tables. A ruleset provides a unit of<br /> execution for rules and for Decision Tables. In addition, rulesets provide a unit of sharing for rules; rules belong to a ruleset.<br /> <br /> A '''Ruleset''' is a set of rules and rule artifacts that can be executed by the engine.<br /> <br /> A '''Ruleset''' contains a collection of rule classes along with the semantics for forward-chaining execution of those rules. A Ruleset<br /> can be executed directly in code or by using the Policy Activity activity<br /> |-<br /> |<br /> |icon<br /> <br /> Decision Table<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> <br /> [[ Image:Logo ibm.png | 100px]] <br /> <br /> IBM WebSphere<br /> <br /> [[ Image:Microsoft.png | 100px]] <br /> <br /> Microsoft .NET<br /> |A '''Decision Table''' defines decisions based on a number of given conditions and actions. Decision tables allow to work from<br /> the same information, and are therefore a precise way to model complicated logics and associations.<br /> <br /> A '''Decision Table''' can either be a tabular representation of related rules or a precise yet compact way to map complicated logic. Decision tables, like flowcharts and if-then-else and switch-case statements, associate conditions with actions to perform, but in many cases do so in a more elegant way.<br /> <br /> An example of using a '''Decision Table''' is an activity to evaluate based on the region and the total amount of the order, whether<br /> or not the approval of a supervisor is required or not. Would be good to have this as a reusable task instead of embedded in<br /> the gateway. The gateway can then just do the branching. Could include a link to a spreadsheet for example.<br /> <br /> '''Decision Tables''' provide an alternative way of viewing and managing large sets of symmetric business rules. A decision table<br /> contains condition columns and action columns.<br /> <br /> '''Decision Tables''' are a simple and clean method of representing large sets of business rules<br /> |-<br /> |<br /> |icon <br /> <br /> Rule Script<br /> |<br /> <br /> [[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> <br /> [[ Image:Logo ibm.png | 100px]] <br /> <br /> IBM WebSphere<br /> |'''Rule Flows''' are comprised of linked tasks that contain the instructions for which rules to execute and in what order. The rules are organized into tasks, and the rule flow specifies how tasks are chained together; how, when, and under what conditions<br /> they are executed. When you are dealing with many large rulesets, managing the order in which rules are evaluated can become complex. Rule flows allows you to specify the order in which rulesets are to be evaluated. It does so by providing you with a flow chart. Use this chart to define which rule sets should be evaluated in sequence, and which ones in parallel, and to specify conditions under which rule sets should be evaluated. The reuse of rules components and their natural relations like activity association are an important aspect of rule modelling principles. This allows for rule modelling consistency between the different rule artifacts from the rule flows, rule scripts, rulesets, flow rulesets, rules and decision tables.<br /> <br /> In order to do advanced project or business area rule modelling, it might be necessary to categorize some of the rules into<br /> main and sub rules. A project can contain many rule flows, one of which must be identified as the main rule flow of the project or area. Additional rule flows could then be added and modelled from the main rule flow. Other rule flows are then included through sub flow tasks.<br /> <br /> A '''Rule Flow''' is a sequence of activities for evaluating business rules. The order of the execution of the rules is diagrammatically<br /> represented in the form of a flow chart. It is a reusable entity within a flow ruleset, and is based on activities associated with artifacts such as rule scripts, rule flows, rulesets, flow rulesets, rules and decision tables.<br /> <br /> Multiple rulesets can be executed in order. This is called a '''Rule Flow'''. The ruleset stack determines the order. The order can be manipulated by rule actions that push and pop rulesets on the stack. In rulesets, the priority of rules applies to specify the order of firing of the rules in the ruleset. Rulesets also provide an effective date specification that identifies that the ruleset is always active, or that the ruleset is restricted based on a time and date range, or a starting or ending time and date.<br /> <br /> A '''Rule Flow''' defines the flow of execution of the rules. The rules are organized into tasks and the ruleflow specifies how tasks<br /> are chained together; how, when, and under what conditions they are executed.<br /> |-<br /> |<br /> |icon<br /> <br /> Rule Script<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> [[ Image:Microsoft.png | 100px]] <br /> <br /> Microsoft .NET<br /> |A '''Rule Script''' allows generating a rule in a scripting environment. This is done through the connection of other activities and the rules that govern these relations, and the actions between them. Rule scripts can furthermore be used with script types, and thereby automated test rules (e.g. configurable, programmed, query and event-based network alerts). The link between rule scripts and the mentioned script type could be used as template–based query that can be run against backend tables or database views.<br /> <br /> A '''Rule Script''' is a reusable artifact within a flow ruleset and is a sequence of actions. It is associated with other activities in a flow ruleset, and is triggered when the conditions listed in the preceding activities are satisfied.<br /> <br /> A rule script can contain any of the following action types: Assign Action, Assert Action, Evaluate Decision, Table Action,<br /> Execute Action, Execute Ruleset Action, Execute Rule Action, For Each Action, If Else, If Action, While Action, Retract Action, Break and Continue Actions.<br /> <br /> The '''Rule Script''' allows to generate a rule from a scripting environment.<br /> |}<br /> [[Category:Objects]]<br /> {{DISPLAYTITLE:X-BPMN Notations}}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=Objects:BPMN_2.0_versus_eXtended_BPMN_(X-BPMN)&diff=912 2015-07-20T13:31:16Z

<p>Fbajohr: </p> <hr /> <div>'''Business Process Representation'''Business process modelling is the discipline of graphically representing a process into a readable diagram. The Business Process Modelling Notation (BPMN) is a graphical notation that depicts the steps in an end to end flow of a business process. The notation has been specifically designed to coordinate the sequence of processes and the messages that flow between different process participants in a related set of activities. BPMN is a vendor neutral, world-wide accepted standard managed by the Object Management Group (OMG) that provides a common way to model business processes. It offers both the simplicity and complexity required to model business processes for both the business audience as well as the technical audience. The LEAD Process Mapping standards is released as a part of the LEADing Practices and will be subject to continuous improvement and development.<br /> <br /> &lt;br/&gt;<br /> <br /> '''History of Business Process Modelling Notations'''<br /> <br /> • March 2001: BPMI members began discussing the idea of creating a notation to go along with the executable BPML. <br /> <br /> • August 2004: BPMN 1.0 specification was released to the public.<br /> • Now maintained by the Object Management Group (OMG). <br /> <br /> • January 2011: BPMN 2.0 specification was released to the public. <br /> <br /> &lt;br/&gt;<br /> <br /> '''LEADing Practice''' then further developed upon the BPMN 2.0 specification to include linkage to: <br /> <br /> • Business Competencies (January 2011). <br /> <br /> • Service Mapping (January 2011). <br /> <br /> • Interaction Models (March 2011). <br /> <br /> • RACI Mapping (May 2011). <br /> <br /> • Value Mapping (November 2011). <br /> <br /> • SAP Netweaver connection (January 2012). <br /> <br /> • SAP Solution Manager connection (February 2012). <br /> <br /> • Incorporation of LEAD X-BPMN principles into iGrafx (November 2012).<br /> <br /> BPMN 2.0 versus eXtended BPMN (X-BPMN) Process Modelling<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;margin: 1em auto 1em auto;&quot;<br /> |+<br /> |- <br /> ! BPMN 2.0 !! X-BPMN !! Source !! scope=&quot;col&quot; width=&quot;75%&quot; | Description <br /> <br /> |- <br /> ||| [[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Rule-01.png | 30px ]] <br /> Rule <br /> <br /> || [[ Image:Leadin.png | 100px]] <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> <br /> [[ Image:Logo ibm.png | 100px]] <br /> <br /> IBM WebSphere<br /> <br /> <br /> [[ Image:Microsoft.png | 100px]] <br /> <br /> Microsoft .NET <br /> || A '''Rule''' is a statement describing a business policy or decision procedure. Some programming languages run business rules<br /> together in very complex algorithms. In business process analysis, each rule is usually stated independently, in the general<br /> format of: If A and B, Then C.<br /> <br /> Workflow tools and detailed process diagrams both depend on business rules to specify how decisions are made. We generally associate business rules with activities. A decision table is adequate to show what happens if A or B happens, but dozens<br /> or even hundreds of business rules may need to be defined to clarify if A or B should happen. Training programs, job aids,<br /> software systems, and knowledge management systems aim to document business rules either to automate the decision<br /> process or to and make the rules available to other decision makers.<br /> <br /> A '''Rule''' is a set of conditions and associated actions that are performed when the conditions are satisfied. Rules can be written<br /> in two forms: as If and Then-statements, and as Decision Tables.<br /> <br /> Business '''Rules''' are statements that describe business policies or describe key business decisions.<br /> <br /> An action '''Rule''' is made of a condition part and of an action part. The first part of the rule defines the condition in which the<br /> rule applies. The second part of the rule defines the action to take if the condition of the rule is true.<br /> <br /> A '''Rule''' defines a condition with an associated set of actions to perform. Rules can be related to:<br /> <br /> • Active: Gets or sets a value that indicates whether the Rule should be evaluated.<br /> <br /> • Condition: Gets or sets a RuleCondition for the Rule to evaluate.<br /> <br /> • Description: Gets or sets a description of the Rule.<br /> <br /> • ElseActions: Gets a collection of RuleAction classes to perform in the ELSE case.<br /> <br /> • Name: Gets or sets the name of the Rule.<br /> <br /> • Priority: Gets or sets a value that indicates the order in which a Rule should be run.<br /> <br /> • Reevaluation: Behavior gets or sets a value indicating whether a Rule can be reevaluated.<br /> <br /> • ThenActions: Gets a collection of RuleAction classes to perform in the THEN case.<br /> |-<br /> |<br /> | [[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Flow_Ruleset-01.png | 30px]] <br /> Flow Ruleset <br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> | A '''Flow Ruleset''' is a collection (and thereby grouping) of rules that apply to a flow. These flow rulesets are either grouped<br /> based on common related rules in the flow, decisions tables, or the need to govern a specific set or behavior of tasks in the<br /> flow. Grouping such flow rulesets allows for sharing of rules and execution, by a rule engine throughout the entire flow. As<br /> well as the relation to the reuse of such rulsets in other flows, starting from the main flow where the ruleset are applied.<br /> <br /> A '''Flow Ruleset''' is a ruleset that allows you to group business rules that need to be executed as in a flow chart. It always has<br /> one flow, designated as main flow, besides possibly many other rule flows. The execution of the Flow Ruleset starts with the<br /> main flow. A Flow Ruleset consists of: Aliases, Definition, Rule Flow, Rule Scripts, If-Then Rules and Decision Tables.<br /> |-<br /> |<br /> |[[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Notification-01.png | 30px]]<br /> <br /> Notification<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> |An instance of a message delivered to one or more recipients. A '''Notification''' activity sends a message to a user, both the<br /> recipients and the content that needs to be specified. Notification activities furthermore allow flow rulesets to be applied in<br /> order to notify users of events that occur during the workflow.<br /> <br /> A '''Notification''' provides often through technology a means of delivering a message to a set of recipients. One need to specify<br /> the recipients and then parameterize the subject and message that are sent.<br /> <br /> The '''Notification''' task allows you to send different types of notifications to the users of the application.<br /> |-<br /> |<br /> |[[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Mapping-01.png | 30px]]<br /> Mapping<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> |'''Mapping''' activities includes identifying, defining and plotting the involved business, information and data objects within the<br /> activities. This allows to identify possible grouping of common business, information and data objects and their associated<br /> rules (e.g. rulesets), enabling the change of complex objects and views into more simple views.<br /> <br /> A '''Mapping''' activity can be used to transform complex objects into more simple views (e.g. map data from data objects in the<br /> specific process context making it more simple data). Rules set can be used as a transform in a mapping activity. To make the<br /> mapping activity work, the mappings between the business, information and data objects in the process context needs to be<br /> defined.<br /> |-<br /> |<br /> | [[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Reporting-01.png | 30px]]<br /> Reporting<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> |'''Reporting''' is the exposure, description and portrayment of specific tasks, services and the associated information and data. The information and data objects/source can bind with the reporting activity the process components to the specific cockpits,<br /> dashboards or scorecards.<br /> <br /> To illustrate and express what is happening, or what has already happened, includes timely collection, analysis and then reporting of the information within the process. Depending if it is real time reporting or after the fact reporting, the input mapping needs to be specified.<br /> <br /> A '''Reporting''' activity is used to collect data and information in order to perform analytics on this data. The reporting activity<br /> references a reporting data source and indicates where in the process data is gathered for reporting. An input mapping<br /> needs to be defined for the reporting activity to specify which data from the process context is collected by the reporting<br /> activity.<br /> |-<br /> |<br /> |icon<br /> <br /> Business Object<br /> <br /> icon<br /> <br /> Collection of <br /> <br /> Business objects<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> |A '''Business Object''' is the term used to express real-world objects like people, employee, products or a sales order, customer and revenue. Business Objects used for example in business, process and service mapping and furthermore used in application<br /> implementations where they are used as a patented semantic layer that shields users from the complexities of information<br /> table names and data relationships.<br /> <br /> Below is a list of the different kinds of Business Objects that are commonly used in business modeling, process mapping and service mapping as well as in application and/or architectural mapping (e.g. business architecture, application architecture<br /> and solution architecture):<br /> <br /> • '''Business Object''' - Represents real-world objects like people, employee, products or a sales order, customer and revenue.<br /> <br /> • '''Collection of Business Objects''' - Represents a collection of real-world objects, e.g. a employee roles.<br /> <br /> • '''Business Input''' - Is an external input for the real-world objects. A kind of input parameter<br /> <br /> • '''Business Output''' - Is the real-world result of the entire process and or service flow. A kind of output parameter.<br /> <br /> • '''Business Store''' - Is a place where the real-world objects are stored.<br /> |-<br /> |<br /> |icon<br /> Information Object<br /> <br /> Collection of<br /> <br /> Information Objects<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> |An '''Information Object''' is used to specify information about real-world objects (like people, employees, products or a sales order, etc.), and is therefore a digital representation of an existing entity within an Information System (e.g. Oracle ERP or SAP<br /> ERP). It encompasses both the business information (in the form of functions and methods) and the application information (in the form of attributes) of the entity. Information Objects can be found and therefore modeled in business functions, business services and business processes.<br /> <br /> Below is a list of the different kinds of Information Objects used in business modeling, process mapping and service mapping as well as in application and/or architectural mapping (e.g. business architecture, information architecture, application architecture and solution architecture):<br /> <br /> • '''Information Object''' - Represents a container of information within the flow of the process and or service, such as business<br /> documents, e-mails, or letters.<br /> <br /> &lt;nowiki&gt; &lt;/nowiki&gt;• '''Collection of Information Objects''' - Represents a collection of information (e.g. a list of order items).<br /> <br /> • '''Information Input''' - Is an external information input for the entire process. A kind of input parameter.<br /> <br /> • '''Information Output''' - Is the information output/result of the entire process. A kind of output parameter.<br /> <br /> • '''Information Store''' - Is a place where the information can be read or written (e.g. knowledge management or a filing cabinet). It persists beyond the lifetime of the process instance.<br /> |-<br /> |<br /> |icon<br /> Data Object<br /> <br /> icon<br /> <br /> Collection of <br /> <br /> Data objects<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> |A Data Object is a logical cluster of all tables in the data set that have one or more columns containing data related to the same business entity. Data objects are not maps, but instead represent an object view of related Information Objects and they represent Business Objects.<br /> <br /> Below is a list of the different kinds of Data Objects used in process mapping and service mapping as well as in application<br /> and/or architectural mapping (e.g. information architecture, application architecture, solution architecture and data architecture):<br /> <br /> • '''Data Object''' - Represents a container/logical cluster of all tables in the data set that have one or more columns containing data related to the same data entity, such as business documents, e-mails, or letters.<br /> <br /> • '''Collection of Data Objects''' - Represents a collection of data tables/columns containing data related to the same data entity (e.g. a list of order items).<br /> <br /> • '''Data Input''' - Is an external data input for the entire process. A kind of input parameter.<br /> <br /> • '''Data Output''' - Is the data result of the entire process. A kind of output parameter.<br /> <br /> • '''Data Store''' - Is a place where the process can read or write data (e.g. a database or a filing cabinet). It persists beyond the lifetime of the process instance.<br /> |-<br /> |None<br /> |None<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |No special task type is indicated.<br /> |-<br /> |icon<br /> User<br /> |icon<br /> User<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''User Task''' is a typical “workflow” task where a human performer performs the task with the assistance of a software application<br /> and is scheduled through a task list manager of some sort.<br /> |-<br /> |icon<br /> Manual<br /> |icon<br /> Manual Task<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Manual Task''' is a task that is expected to be performed without the aid of any business process execution engine or any<br /> application.<br /> |-<br /> |<br /> |icon<br /> Automated Task<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> |An '''Automated Task''' is an activity that is automated through either a business process execution engine or any application<br /> (e.g. using application features and/or functions to enable the application task).<br /> |-<br /> |icon<br /> Service<br /> |<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Service Task''' is a task that uses some sort of service which could be a web service or an automated application.<br /> |-<br /> |<br /> |icon<br /> Manual Service<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> |A '''Manual Service''' is when the service is performed by a human.<br /> |-<br /> |<br /> |icon<br /> <br /> Automated Service<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> |An '''Automated Service''' can be either an application service, data service, platform service, infrastructure service or a web<br /> service.<br /> |-<br /> |icon<br /> <br /> Send<br /> |icon<br /> <br /> Send<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Send Task''' is a simple task that is designed to send a message to an external participant (relative to the process).<br /> |-<br /> |icon<br /> <br /> Receive<br /> |icon<br /> <br /> Receive<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Receive Tas'''k is a simple task that is designed to wait for a message to arrive from an external participant (relative to the<br /> process).<br /> |-<br /> |icon<br /> <br /> Script<br /> |icon<br /> <br /> Script<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Script Task''' is executed by a business process engine. The modeler or implementer defines a script in a language that the<br /> engine can interpret, and when the task is ready to start, the engine will execute the script. When the script is completed, the<br /> task will also be completed.<br /> |-<br /> |icon<br /> <br /> Business Rule<br /> |icon<br /> <br /> Business Rule<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Business Rule Task''' provides a mechanism for the process to provide input to a business rules engine, and to get the output<br /> of calculations that the business rules engine might provide. The input/output specification of the task will allow the process<br /> to send data to and receive data from the business rules engine.<br /> |-<br /> |<br /> |icon<br /> <br /> Ruleset<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> <br /> [[ Image:Logo ibm.png | 100px]] <br /> <br /> IBM WebSphere<br /> <br /> [[ Image:Microsoft.png | 100px]] <br /> <br /> Microsoft .NET<br /> |A '''Ruleset''' is a collection (and thereby a grouping) of rules. They are either grouped based on common related rules, decisions tables or the need to govern a specific set or behavior of tasks. Grouping such rulesets allows for sharing of rules and execution by a rules engine.<br /> <br /> A '''Ruleset''' is a logical collection of rules. A ruleset helps you group business rules that govern a specific function. A ruleset<br /> consists of: If-Then Rules and Decision Tables.<br /> <br /> A '''Ruleset''' is a container that includes definitions for a group of related rules and decision tables. A ruleset provides a unit of<br /> execution for rules and for Decision Tables. In addition, rulesets provide a unit of sharing for rules; rules belong to a ruleset.<br /> <br /> A '''Ruleset''' is a set of rules and rule artifacts that can be executed by the engine.<br /> <br /> A '''Ruleset''' contains a collection of rule classes along with the semantics for forward-chaining execution of those rules. A Ruleset<br /> can be executed directly in code or by using the Policy Activity activity<br /> |-<br /> |<br /> |icon<br /> <br /> Decision Table<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> <br /> [[ Image:Logo ibm.png | 100px]] <br /> <br /> IBM WebSphere<br /> <br /> [[ Image:Microsoft.png | 100px]] <br /> <br /> Microsoft .NET<br /> |A '''Decision Table''' defines decisions based on a number of given conditions and actions. Decision tables allow to work from<br /> the same information, and are therefore a precise way to model complicated logics and associations.<br /> <br /> A '''Decision Table''' can either be a tabular representation of related rules or a precise yet compact way to map complicated logic. Decision tables, like flowcharts and if-then-else and switch-case statements, associate conditions with actions to perform, but in many cases do so in a more elegant way.<br /> <br /> An example of using a '''Decision Table''' is an activity to evaluate based on the region and the total amount of the order, whether<br /> or not the approval of a supervisor is required or not. Would be good to have this as a reusable task instead of embedded in<br /> the gateway. The gateway can then just do the branching. Could include a link to a spreadsheet for example.<br /> <br /> '''Decision Tables''' provide an alternative way of viewing and managing large sets of symmetric business rules. A decision table<br /> contains condition columns and action columns.<br /> <br /> '''Decision Tables''' are a simple and clean method of representing large sets of business rules<br /> |-<br /> |<br /> |icon <br /> <br /> Rule Script<br /> |<br /> <br /> [[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> <br /> [[ Image:Logo ibm.png | 100px]] <br /> <br /> IBM WebSphere<br /> |'''Rule Flows''' are comprised of linked tasks that contain the instructions for which rules to execute and in what order. The rules are organized into tasks, and the rule flow specifies how tasks are chained together; how, when, and under what conditions<br /> they are executed. When you are dealing with many large rulesets, managing the order in which rules are evaluated can become complex. Rule flows allows you to specify the order in which rulesets are to be evaluated. It does so by providing you with a flow chart. Use this chart to define which rule sets should be evaluated in sequence, and which ones in parallel, and to specify conditions under which rule sets should be evaluated. The reuse of rules components and their natural relations like activity association are an important aspect of rule modelling principles. This allows for rule modelling consistency between the different rule artifacts from the rule flows, rule scripts, rulesets, flow rulesets, rules and decision tables.<br /> <br /> In order to do advanced project or business area rule modelling, it might be necessary to categorize some of the rules into<br /> main and sub rules. A project can contain many rule flows, one of which must be identified as the main rule flow of the project or area. Additional rule flows could then be added and modelled from the main rule flow. Other rule flows are then included through sub flow tasks.<br /> <br /> A '''Rule Flow''' is a sequence of activities for evaluating business rules. The order of the execution of the rules is diagrammatically<br /> represented in the form of a flow chart. It is a reusable entity within a flow ruleset, and is based on activities associated with artifacts such as rule scripts, rule flows, rulesets, flow rulesets, rules and decision tables.<br /> <br /> Multiple rulesets can be executed in order. This is called a '''Rule Flow'''. The ruleset stack determines the order. The order can be manipulated by rule actions that push and pop rulesets on the stack. In rulesets, the priority of rules applies to specify the order of firing of the rules in the ruleset. Rulesets also provide an effective date specification that identifies that the ruleset is always active, or that the ruleset is restricted based on a time and date range, or a starting or ending time and date.<br /> <br /> A '''Rule Flow''' defines the flow of execution of the rules. The rules are organized into tasks and the ruleflow specifies how tasks<br /> are chained together; how, when, and under what conditions they are executed.<br /> |-<br /> |<br /> |icon<br /> <br /> Rule Script<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> [[ Image:Microsoft.png | 100px]] <br /> <br /> Microsoft .NET<br /> |A '''Rule Script''' allows generating a rule in a scripting environment. This is done through the connection of other activities and the rules that govern these relations, and the actions between them. Rule scripts can furthermore be used with script types, and thereby automated test rules (e.g. configurable, programmed, query and event-based network alerts). The link between rule scripts and the mentioned script type could be used as template–based query that can be run against backend tables or database views.<br /> <br /> A '''Rule Script''' is a reusable artifact within a flow ruleset and is a sequence of actions. It is associated with other activities in a flow ruleset, and is triggered when the conditions listed in the preceding activities are satisfied.<br /> <br /> A rule script can contain any of the following action types: Assign Action, Assert Action, Evaluate Decision, Table Action,<br /> Execute Action, Execute Ruleset Action, Execute Rule Action, For Each Action, If Else, If Action, While Action, Retract Action, Break and Continue Actions.<br /> <br /> The '''Rule Script''' allows to generate a rule from a scripting environment.<br /> |}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Reporting-01.png&diff=911 2015-07-20T13:22:58Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Mapping-01.png&diff=910 2015-07-20T13:22:10Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Notification-01.png&diff=909 2015-07-20T13:20:26Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Flow_Ruleset-01.png&diff=908 2015-07-20T13:15:05Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=Objects:BPMN_2.0_versus_eXtended_BPMN_(X-BPMN)&diff=907 2015-07-20T13:13:30Z

<p>Fbajohr: </p> <hr /> <div>'''Business Process Representation'''Business process modelling is the discipline of graphically representing a process into a readable diagram. The Business Process Modelling Notation (BPMN) is a graphical notation that depicts the steps in an end to end flow of a business process. The notation has been specifically designed to coordinate the sequence of processes and the messages that flow between different process participants in a related set of activities. BPMN is a vendor neutral, world-wide accepted standard managed by the Object Management Group (OMG) that provides a common way to model business processes. It offers both the simplicity and complexity required to model business processes for both the business audience as well as the technical audience. The LEAD Process Mapping standards is released as a part of the LEADing Practices and will be subject to continuous improvement and development.<br /> <br /> &lt;br/&gt;<br /> <br /> '''History of Business Process Modelling Notations'''<br /> <br /> • March 2001: BPMI members began discussing the idea of creating a notation to go along with the executable BPML. <br /> <br /> • August 2004: BPMN 1.0 specification was released to the public.<br /> • Now maintained by the Object Management Group (OMG). <br /> <br /> • January 2011: BPMN 2.0 specification was released to the public. <br /> <br /> &lt;br/&gt;<br /> <br /> '''LEADing Practice''' then further developed upon the BPMN 2.0 specification to include linkage to: <br /> <br /> • Business Competencies (January 2011). <br /> <br /> • Service Mapping (January 2011). <br /> <br /> • Interaction Models (March 2011). <br /> <br /> • RACI Mapping (May 2011). <br /> <br /> • Value Mapping (November 2011). <br /> <br /> • SAP Netweaver connection (January 2012). <br /> <br /> • SAP Solution Manager connection (February 2012). <br /> <br /> • Incorporation of LEAD X-BPMN principles into iGrafx (November 2012).<br /> <br /> BPMN 2.0 versus eXtended BPMN (X-BPMN) Process Modelling<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;margin: 1em auto 1em auto;&quot;<br /> |+<br /> |- <br /> ! BPMN 2.0 !! X-BPMN !! Source !! scope=&quot;col&quot; width=&quot;75%&quot; | Description <br /> <br /> |- <br /> ||| [[ Image:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Rule-01.png | 40px ]] <br /> Rule <br /> <br /> || [[ Image:Leadin.png | 100px]] <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> <br /> [[ Image:Logo ibm.png | 100px]] <br /> <br /> IBM WebSphere<br /> <br /> <br /> [[ Image:Microsoft.png | 100px]] <br /> <br /> Microsoft .NET <br /> || A '''Rule''' is a statement describing a business policy or decision procedure. Some programming languages run business rules<br /> together in very complex algorithms. In business process analysis, each rule is usually stated independently, in the general<br /> format of: If A and B, Then C.<br /> <br /> Workflow tools and detailed process diagrams both depend on business rules to specify how decisions are made. We generally associate business rules with activities. A decision table is adequate to show what happens if A or B happens, but dozens<br /> or even hundreds of business rules may need to be defined to clarify if A or B should happen. Training programs, job aids,<br /> software systems, and knowledge management systems aim to document business rules either to automate the decision<br /> process or to and make the rules available to other decision makers.<br /> <br /> A '''Rule''' is a set of conditions and associated actions that are performed when the conditions are satisfied. Rules can be written<br /> in two forms: as If and Then-statements, and as Decision Tables.<br /> <br /> Business '''Rules''' are statements that describe business policies or describe key business decisions.<br /> <br /> An action '''Rule''' is made of a condition part and of an action part. The first part of the rule defines the condition in which the<br /> rule applies. The second part of the rule defines the action to take if the condition of the rule is true.<br /> <br /> A '''Rule''' defines a condition with an associated set of actions to perform. Rules can be related to:<br /> <br /> • Active: Gets or sets a value that indicates whether the Rule should be evaluated.<br /> <br /> • Condition: Gets or sets a RuleCondition for the Rule to evaluate.<br /> <br /> • Description: Gets or sets a description of the Rule.<br /> <br /> • ElseActions: Gets a collection of RuleAction classes to perform in the ELSE case.<br /> <br /> • Name: Gets or sets the name of the Rule.<br /> <br /> • Priority: Gets or sets a value that indicates the order in which a Rule should be run.<br /> <br /> • Reevaluation: Behavior gets or sets a value indicating whether a Rule can be reevaluated.<br /> <br /> • ThenActions: Gets a collection of RuleAction classes to perform in the THEN case.<br /> |-<br /> |<br /> | icon <br /> Flow Ruleset <br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> | A '''Flow Ruleset''' is a collection (and thereby grouping) of rules that apply to a flow. These flow rulesets are either grouped<br /> based on common related rules in the flow, decisions tables, or the need to govern a specific set or behavior of tasks in the<br /> flow. Grouping such flow rulesets allows for sharing of rules and execution, by a rule engine throughout the entire flow. As<br /> well as the relation to the reuse of such rulsets in other flows, starting from the main flow where the ruleset are applied.<br /> <br /> A '''Flow Ruleset''' is a ruleset that allows you to group business rules that need to be executed as in a flow chart. It always has<br /> one flow, designated as main flow, besides possibly many other rule flows. The execution of the Flow Ruleset starts with the<br /> main flow. A Flow Ruleset consists of: Aliases, Definition, Rule Flow, Rule Scripts, If-Then Rules and Decision Tables.<br /> |-<br /> |<br /> |icon<br /> <br /> Notification<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> |An instance of a message delivered to one or more recipients. A '''Notification''' activity sends a message to a user, both the<br /> recipients and the content that needs to be specified. Notification activities furthermore allow flow rulesets to be applied in<br /> order to notify users of events that occur during the workflow.<br /> <br /> A '''Notification''' provides often through technology a means of delivering a message to a set of recipients. One need to specify<br /> the recipients and then parameterize the subject and message that are sent.<br /> <br /> The '''Notification''' task allows you to send different types of notifications to the users of the application.<br /> |-<br /> |<br /> |icon<br /> Mapping<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> |'''Mapping''' activities includes identifying, defining and plotting the involved business, information and data objects within the<br /> activities. This allows to identify possible grouping of common business, information and data objects and their associated<br /> rules (e.g. rulesets), enabling the change of complex objects and views into more simple views.<br /> <br /> A '''Mapping''' activity can be used to transform complex objects into more simple views (e.g. map data from data objects in the<br /> specific process context making it more simple data). Rules set can be used as a transform in a mapping activity. To make the<br /> mapping activity work, the mappings between the business, information and data objects in the process context needs to be<br /> defined.<br /> |-<br /> |<br /> |icon<br /> Reporting<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> |'''Reporting''' is the exposure, description and portrayment of specific tasks, services and the associated information and data. The information and data objects/source can bind with the reporting activity the process components to the specific cockpits,<br /> dashboards or scorecards.<br /> <br /> To illustrate and express what is happening, or what has already happened, includes timely collection, analysis and then reporting of the information within the process. Depending if it is real time reporting or after the fact reporting, the input mapping needs to be specified.<br /> <br /> A '''Reporting''' activity is used to collect data and information in order to perform analytics on this data. The reporting activity<br /> references a reporting data source and indicates where in the process data is gathered for reporting. An input mapping<br /> needs to be defined for the reporting activity to specify which data from the process context is collected by the reporting<br /> activity.<br /> |-<br /> |<br /> |icon<br /> <br /> Business Object<br /> <br /> icon<br /> <br /> Collection of <br /> <br /> Business objects<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> |A '''Business Object''' is the term used to express real-world objects like people, employee, products or a sales order, customer and revenue. Business Objects used for example in business, process and service mapping and furthermore used in application<br /> implementations where they are used as a patented semantic layer that shields users from the complexities of information<br /> table names and data relationships.<br /> <br /> Below is a list of the different kinds of Business Objects that are commonly used in business modeling, process mapping and service mapping as well as in application and/or architectural mapping (e.g. business architecture, application architecture<br /> and solution architecture):<br /> <br /> • '''Business Object''' - Represents real-world objects like people, employee, products or a sales order, customer and revenue.<br /> <br /> • '''Collection of Business Objects''' - Represents a collection of real-world objects, e.g. a employee roles.<br /> <br /> • '''Business Input''' - Is an external input for the real-world objects. A kind of input parameter<br /> <br /> • '''Business Output''' - Is the real-world result of the entire process and or service flow. A kind of output parameter.<br /> <br /> • '''Business Store''' - Is a place where the real-world objects are stored.<br /> |-<br /> |<br /> |icon<br /> Information Object<br /> <br /> Collection of<br /> <br /> Information Objects<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> |An '''Information Object''' is used to specify information about real-world objects (like people, employees, products or a sales order, etc.), and is therefore a digital representation of an existing entity within an Information System (e.g. Oracle ERP or SAP<br /> ERP). It encompasses both the business information (in the form of functions and methods) and the application information (in the form of attributes) of the entity. Information Objects can be found and therefore modeled in business functions, business services and business processes.<br /> <br /> Below is a list of the different kinds of Information Objects used in business modeling, process mapping and service mapping as well as in application and/or architectural mapping (e.g. business architecture, information architecture, application architecture and solution architecture):<br /> <br /> • '''Information Object''' - Represents a container of information within the flow of the process and or service, such as business<br /> documents, e-mails, or letters.<br /> <br /> &lt;nowiki&gt; &lt;/nowiki&gt;• '''Collection of Information Objects''' - Represents a collection of information (e.g. a list of order items).<br /> <br /> • '''Information Input''' - Is an external information input for the entire process. A kind of input parameter.<br /> <br /> • '''Information Output''' - Is the information output/result of the entire process. A kind of output parameter.<br /> <br /> • '''Information Store''' - Is a place where the information can be read or written (e.g. knowledge management or a filing cabinet). It persists beyond the lifetime of the process instance.<br /> |-<br /> |<br /> |icon<br /> Data Object<br /> <br /> icon<br /> <br /> Collection of <br /> <br /> Data objects<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> |A Data Object is a logical cluster of all tables in the data set that have one or more columns containing data related to the same business entity. Data objects are not maps, but instead represent an object view of related Information Objects and they represent Business Objects.<br /> <br /> Below is a list of the different kinds of Data Objects used in process mapping and service mapping as well as in application<br /> and/or architectural mapping (e.g. information architecture, application architecture, solution architecture and data architecture):<br /> <br /> • '''Data Object''' - Represents a container/logical cluster of all tables in the data set that have one or more columns containing data related to the same data entity, such as business documents, e-mails, or letters.<br /> <br /> • '''Collection of Data Objects''' - Represents a collection of data tables/columns containing data related to the same data entity (e.g. a list of order items).<br /> <br /> • '''Data Input''' - Is an external data input for the entire process. A kind of input parameter.<br /> <br /> • '''Data Output''' - Is the data result of the entire process. A kind of output parameter.<br /> <br /> • '''Data Store''' - Is a place where the process can read or write data (e.g. a database or a filing cabinet). It persists beyond the lifetime of the process instance.<br /> |-<br /> |None<br /> |None<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |No special task type is indicated.<br /> |-<br /> |icon<br /> User<br /> |icon<br /> User<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''User Task''' is a typical “workflow” task where a human performer performs the task with the assistance of a software application<br /> and is scheduled through a task list manager of some sort.<br /> |-<br /> |icon<br /> Manual<br /> |icon<br /> Manual Task<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Manual Task''' is a task that is expected to be performed without the aid of any business process execution engine or any<br /> application.<br /> |-<br /> |<br /> |icon<br /> Automated Task<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> |An '''Automated Task''' is an activity that is automated through either a business process execution engine or any application<br /> (e.g. using application features and/or functions to enable the application task).<br /> |-<br /> |icon<br /> Service<br /> |<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Service Task''' is a task that uses some sort of service which could be a web service or an automated application.<br /> |-<br /> |<br /> |icon<br /> Manual Service<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> |A '''Manual Service''' is when the service is performed by a human.<br /> |-<br /> |<br /> |icon<br /> <br /> Automated Service<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> |An '''Automated Service''' can be either an application service, data service, platform service, infrastructure service or a web<br /> service.<br /> |-<br /> |icon<br /> <br /> Send<br /> |icon<br /> <br /> Send<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Send Task''' is a simple task that is designed to send a message to an external participant (relative to the process).<br /> |-<br /> |icon<br /> <br /> Receive<br /> |icon<br /> <br /> Receive<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Receive Tas'''k is a simple task that is designed to wait for a message to arrive from an external participant (relative to the<br /> process).<br /> |-<br /> |icon<br /> <br /> Script<br /> |icon<br /> <br /> Script<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Script Task''' is executed by a business process engine. The modeler or implementer defines a script in a language that the<br /> engine can interpret, and when the task is ready to start, the engine will execute the script. When the script is completed, the<br /> task will also be completed.<br /> |-<br /> |icon<br /> <br /> Business Rule<br /> |icon<br /> <br /> Business Rule<br /> |[[ Image:Objectmg-logo.jpg | 100px]] <br /> Object management<br /> <br /> Group<br /> |A '''Business Rule Task''' provides a mechanism for the process to provide input to a business rules engine, and to get the output<br /> of calculations that the business rules engine might provide. The input/output specification of the task will allow the process<br /> to send data to and receive data from the business rules engine.<br /> |-<br /> |<br /> |icon<br /> <br /> Ruleset<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> <br /> [[ Image:Logo ibm.png | 100px]] <br /> <br /> IBM WebSphere<br /> <br /> [[ Image:Microsoft.png | 100px]] <br /> <br /> Microsoft .NET<br /> |A '''Ruleset''' is a collection (and thereby a grouping) of rules. They are either grouped based on common related rules, decisions tables or the need to govern a specific set or behavior of tasks. Grouping such rulesets allows for sharing of rules and execution by a rules engine.<br /> <br /> A '''Ruleset''' is a logical collection of rules. A ruleset helps you group business rules that govern a specific function. A ruleset<br /> consists of: If-Then Rules and Decision Tables.<br /> <br /> A '''Ruleset''' is a container that includes definitions for a group of related rules and decision tables. A ruleset provides a unit of<br /> execution for rules and for Decision Tables. In addition, rulesets provide a unit of sharing for rules; rules belong to a ruleset.<br /> <br /> A '''Ruleset''' is a set of rules and rule artifacts that can be executed by the engine.<br /> <br /> A '''Ruleset''' contains a collection of rule classes along with the semantics for forward-chaining execution of those rules. A Ruleset<br /> can be executed directly in code or by using the Policy Activity activity<br /> |-<br /> |<br /> |icon<br /> <br /> Decision Table<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> <br /> [[ Image:Logo ibm.png | 100px]] <br /> <br /> IBM WebSphere<br /> <br /> [[ Image:Microsoft.png | 100px]] <br /> <br /> Microsoft .NET<br /> |A '''Decision Table''' defines decisions based on a number of given conditions and actions. Decision tables allow to work from<br /> the same information, and are therefore a precise way to model complicated logics and associations.<br /> <br /> A '''Decision Table''' can either be a tabular representation of related rules or a precise yet compact way to map complicated logic. Decision tables, like flowcharts and if-then-else and switch-case statements, associate conditions with actions to perform, but in many cases do so in a more elegant way.<br /> <br /> An example of using a '''Decision Table''' is an activity to evaluate based on the region and the total amount of the order, whether<br /> or not the approval of a supervisor is required or not. Would be good to have this as a reusable task instead of embedded in<br /> the gateway. The gateway can then just do the branching. Could include a link to a spreadsheet for example.<br /> <br /> '''Decision Tables''' provide an alternative way of viewing and managing large sets of symmetric business rules. A decision table<br /> contains condition columns and action columns.<br /> <br /> '''Decision Tables''' are a simple and clean method of representing large sets of business rules<br /> |-<br /> |<br /> |icon <br /> <br /> Rule Script<br /> |<br /> <br /> [[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> <br /> [[ Image:Oracle-logo.png | 100px]] <br /> <br /> Oracle Business Rules<br /> <br /> [[ Image:Logo ibm.png | 100px]] <br /> <br /> IBM WebSphere<br /> |'''Rule Flows''' are comprised of linked tasks that contain the instructions for which rules to execute and in what order. The rules are organized into tasks, and the rule flow specifies how tasks are chained together; how, when, and under what conditions<br /> they are executed. When you are dealing with many large rulesets, managing the order in which rules are evaluated can become complex. Rule flows allows you to specify the order in which rulesets are to be evaluated. It does so by providing you with a flow chart. Use this chart to define which rule sets should be evaluated in sequence, and which ones in parallel, and to specify conditions under which rule sets should be evaluated. The reuse of rules components and their natural relations like activity association are an important aspect of rule modelling principles. This allows for rule modelling consistency between the different rule artifacts from the rule flows, rule scripts, rulesets, flow rulesets, rules and decision tables.<br /> <br /> In order to do advanced project or business area rule modelling, it might be necessary to categorize some of the rules into<br /> main and sub rules. A project can contain many rule flows, one of which must be identified as the main rule flow of the project or area. Additional rule flows could then be added and modelled from the main rule flow. Other rule flows are then included through sub flow tasks.<br /> <br /> A '''Rule Flow''' is a sequence of activities for evaluating business rules. The order of the execution of the rules is diagrammatically<br /> represented in the form of a flow chart. It is a reusable entity within a flow ruleset, and is based on activities associated with artifacts such as rule scripts, rule flows, rulesets, flow rulesets, rules and decision tables.<br /> <br /> Multiple rulesets can be executed in order. This is called a '''Rule Flow'''. The ruleset stack determines the order. The order can be manipulated by rule actions that push and pop rulesets on the stack. In rulesets, the priority of rules applies to specify the order of firing of the rules in the ruleset. Rulesets also provide an effective date specification that identifies that the ruleset is always active, or that the ruleset is restricted based on a time and date range, or a starting or ending time and date.<br /> <br /> A '''Rule Flow''' defines the flow of execution of the rules. The rules are organized into tasks and the ruleflow specifies how tasks<br /> are chained together; how, when, and under what conditions they are executed.<br /> |-<br /> |<br /> |icon<br /> <br /> Rule Script<br /> |[[ Image:Leadin.png | 100px]] <br /> <br /> LEADing Practice<br /> <br /> [[ Image:SAP-Logo.png | 100px]] <br /> <br /> SAP NetWeaver<br /> <br /> [[ Image:Microsoft.png | 100px]] <br /> <br /> Microsoft .NET<br /> |A '''Rule Script''' allows generating a rule in a scripting environment. This is done through the connection of other activities and the rules that govern these relations, and the actions between them. Rule scripts can furthermore be used with script types, and thereby automated test rules (e.g. configurable, programmed, query and event-based network alerts). The link between rule scripts and the mentioned script type could be used as template–based query that can be run against backend tables or database views.<br /> <br /> A '''Rule Script''' is a reusable artifact within a flow ruleset and is a sequence of actions. It is associated with other activities in a flow ruleset, and is triggered when the conditions listed in the preceding activities are satisfied.<br /> <br /> A rule script can contain any of the following action types: Assign Action, Assert Action, Evaluate Decision, Table Action,<br /> Execute Action, Execute Ruleset Action, Execute Rule Action, For Each Action, If Else, If Action, While Action, Retract Action, Break and Continue Actions.<br /> <br /> The '''Rule Script''' allows to generate a rule from a scripting environment.<br /> |}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:Leadin.png&diff=906 2015-07-20T12:27:53Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:Objectmg-logo.jpg&diff=905 2015-07-20T12:20:53Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:Microsoft.png&diff=904 2015-07-20T12:17:49Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:SAP-Logo.png&diff=903 2015-07-20T12:15:50Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:Oracle-logo.png&diff=902 2015-07-20T12:14:26Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:Logo_ibm.png&diff=901 2015-07-20T12:10:23Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:IBM-logo.jpg&diff=900 2015-07-20T12:09:29Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:LEAD_BPMN_2.0_-_Visio_Stencils_-_Activity_Markers_-_Rule-01.png&diff=899 2015-07-20T11:50:58Z

<p>Fbajohr: </p> <hr /> <div>== Licensing ==<br /> {{[[LEADing Practice IP::LEADing Practice IP]] }}</div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:Image152.png&diff=740 2015-07-15T09:03:23Z

<p>Fbajohr: </p> <hr /> <div></div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:Image144.png&diff=739 2015-07-15T09:02:12Z

<p>Fbajohr: </p> <hr /> <div></div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:Image142.png&diff=738 2015-07-15T09:01:44Z

<p>Fbajohr: </p> <hr /> <div></div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:Image078.png&diff=737 2015-07-15T09:00:58Z

<p>Fbajohr: </p> <hr /> <div></div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:Image130.png&diff=736 2015-07-15T09:00:10Z

<p>Fbajohr: </p> <hr /> <div></div>

Fbajohr https://www.workplace.enterpriseplus.tools/index.php?title=File:Image120.png&diff=735 2015-07-15T08:58:29Z

<p>Fbajohr: </p> <hr /> <div></div>

Fbajohr