Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Connectors are used to branch or reconnect the process flow. Two connectors are available in EPCs for modeling: AND and XOR.

Tip

Further information and case examples regarding the use of each connector can be found at AND Branching and XOR Branching.

The AND Connector

Element

Function

During modeling, the AND Connector is used to document that multiple process branches are run through simultaneously. This means: All branches between the AND brackets have to be completed before the process can continue in the main branch.

Connection Predecessor: Function
Successor: Function, Event
Example

A business process intends that completion of a reuqest form triggers three different process branches: The form is evaluated statistically, the buyer receives an answer and the order is processed. 

The first AND Connector opens the parallel execution: The three process chains Evaluating form, Answering request and Processing order are started simultaneously and run independently from each other. The closing AND defines the end of the parallel execution. The process continues with the next step of the main process branch.

Configuration Options

Multiexcerpt include
SpaceWithExcerptINTERNAL
MultiExcerptNameforms_edit_sidebar
PageWithExcerptINTERNAL:_BPaaS_excerpts

Multiexcerpt include
SpaceWithExcerptINTERNAL
MultiExcerptNameform_elements_name
PageWithExcerptINTERNAL:_BPaaS_excerpts

Multiexcerpt include
SpaceWithExcerptINTERNAL
MultiExcerptNamemodel_id
DisableCachingtrue
PageWithExcerptINTERNAL:_BPaaS_excerpts

Multiexcerpt include
SpaceWithExcerptINTERNAL
MultiExcerptNameepc_elements_description
PageWithExcerptINTERNAL:_BPaaS_excerpts

Multiexcerpt include
SpaceWithExcerptINTERNAL
MultiExcerptNameepc_elements_hashtags
DisableCachingtrue
PageWithExcerptINTERNAL:_BPaaS_excerpts

The XOR Connector

Element

Meaning

The connector XOR (= Either-Or) indicates that one of several conditions must be fulfilled. This means that after the XOR, exactly one of several possible process strings is processed.

Connection

Predecessor: Function
Successor: Event

Example

A business process intends that a Procurement Request can be placed. After the action Recording request two possible events can occur: Either the Credit limit adhered or the Credit limit exceeded. Depending on which event occured, a different process string is started. The constraints, that need to be met for either process sring are defined in the element Event.

Configuration Options

Multiexcerpt include
SpaceWithExcerptINTERNAL
MultiExcerptNameepc_elements_edit
PageWithExcerptINTERNAL:_BPaaS_excerpts

Multiexcerpt include
SpaceWithExcerptINTERNAL
MultiExcerptNameepc_elements_name
PageWithExcerptINTERNAL:_BPaaS_excerpts

Multiexcerpt include
SpaceWithExcerptINTERNAL
MultiExcerptNamemodel_id
DisableCachingtrue
PageWithExcerptINTERNAL:_BPaaS_excerpts

Multiexcerpt include
SpaceWithExcerptINTERNAL
MultiExcerptNameepc_elements_description
PageWithExcerptINTERNAL:_BPaaS_excerpts

Multiexcerpt include
SpaceWithExcerptINTERNAL
MultiExcerptNameepc_elements_hashtags
DisableCachingtrue
PageWithExcerptINTERNAL:_BPaaS_excerpts

Branching and Constraints

The AND Connector is tied to a single constraint: All process branches within the AND bracket have to be executed. The main process can only continue once all process branches between the opening and closing AND Connector are processed. Therefore no further constraints need to be defined when using the AND Connector.

The XOR Connector enables issuing multiple constraints. Therefore the XOR Connector is always followed by an Event in which the corresponding constraints for the varying process strings need to be defined.

Multiexcerpt include
SpaceWithExcerptINTERNAL
MultiExcerptNameepc_elements_connector_constraints
PageWithExcerptINTERNAL:_BPaaS_excerpts


Panel
titleOn this Page:
Table of Contents


Panel
titleRelated Pages:

Otp
Floatingfalse
maxHLevel2

rp