This appendix provides information for each of the BPMN flow object properties. It contains these topics:
This section describes common properties shared by multiple BPMN flow objects.
Table A-1 lists the properties that are shared by all activities and gateways. These properties appear in the Basic tab.
Table A-1 Common Properties for Activities and Gateways - Basic Tab
| Property | Description |
|---|---|
|
Name |
Defines the name of this flow object. This becomes the name of the flow object within your process. |
|
Description |
Provides an optional description of this flow object. Adding a description can make your process more readable. |
|
Sampling Point |
Use to configure sampling points for this flow object.
Sampling points enable you to generate information about the performance of an flow object within in a running process. The data generated according to this configuration is stored in the Process Analytics Database. Sampling point generation specified at the project level is applied to all of the processes within the project. See Section 4.4.10, "How to View and Configure Project Properties" for procedures for setting sampling point for a project. However, you can override project-level settings within a process. Likewise, sampling point generation specified at the process level is applied to all of the flow objects within the process. You can also override process-level settings within each flow object. Overriding sampling point generation at the project or process level is usually done to improve performance. For example, if your project contains a process that contains a great number of activities and you are not interested in obtaining process metrics for this process, you might choose to set its sampling point configuration so that the process does not generate sampling points. Likewise, if you are interested in measuring only one process within your project, you might choose to set the project not to generate sampling point and configure that particular process to generate sampling points. By default, the project sampling configuration is set to generate sampling points only for interactive activities. |
The following sections describe the properties of each BPMN activities supported by the Oracle BPM Suite.
The user task represents a part of your process where a process participant is required to perform work.
See Section 6.3.2, "Introduction to the User Task" for more information.
The basic tab of the user task contains properties shared by multiple BPMN flow objects. See Section A.1, "Common Properties" for a list of these properties.
Table A-2 User Task Properties - Counter Tab
| Property | Description |
|---|---|
|
Business Indicators |
Defines the business indicator used as the counter for the human task. See Section 7.3, "Working with Business Indicators and Counter Marks" for more information. |
Table A-3 describes the properties that can be edited from the Implementation tab.
Table A-3 User Task Properties - Implementation Tab
| Property | Description |
|---|---|
|
Human Task |
Defines the name of the human task assigned to this user task. You can select a list of human tasks in the business catalog. |
|
Pattern |
Displays the pattern used for this human task. |
|
Re-initiate |
Restarts the approval process from the beginning. |
The manual task represents a task within a process that is performed by process participants that is outside of the scope of Oracle BPM.
See Section 6.3.3, "Introduction to the Manual Task" for more information.
The basic tab of the manual task contains properties shared by multiple BPMN flow objects. See Section A.1, "Common Properties" for a list of these properties.
The service task enables you to communicate with other processes and services.
See Section 6.4.1, "Introduction to the Service Task" for more information.
The basic tab of the service task contains properties shared by multiple BPMN flow objects. See Section A.1, "Common Properties" for a list of these properties.
Table A-4 describes the properties that can be edited from the Implementation tab when you select the Service option.
The send task sends a message to a system or process outside the current process.
See Section 6.4.3, "Introduction to the Send Task" for more information.
The basic tab of the send task contains properties shared by multiple BPMN flow objects. See Section A.1, "Common Properties" for a list of these properties.
Table A-6 describes basic implementation properties of the send task.
Table A-6 Send Task Properties - Implementation Tab
| Property | Description |
|---|---|
|
Type |
Defines how the conversation of the send task is implemented. A conversation defines the sequence of a group of send and receive tasks that communicate with other processes or services. A send task can start a conversation with another process or service, or continue a conversation initiated by a previous send task. Possible values are:
|
Table A-7 describes the implementation properties available when Initiates is selected.
Table A-7 Send Task Properties - Implementation Tab (When Initiates is Selected)
| Property | Description |
|---|---|
|
Implementation |
The implementation drop-down menu enables you to determine how the send task is implemented.
|
Table A-8 describes the implementation properties when Continues is selected.
The receive task waits for a message from a system or process outside the current process.
See Section 6.4.4, "Introduction to the Receive Task" for more information.
The basic tab of the receive task contains properties shared by multiple BPMN flow objects. See Section A.1, "Common Properties" for a list of these properties.
Table A-9 describes basic implementation properties of the receive task.
Table A-9 Receive Task Properties - Implementation Tab
| Property | Description |
|---|---|
|
Create Instance |
Determines that the receive task will create a new process instance. |
|
Type |
Determines how the conversation of the receive task is implemented. A conversation defines the sequence of a group of send and receive tasks that communicate with other processes or services. A send task can start a conversation with another process or service, or continue a conversation initiated by a previous send task. Possible values are:
|
Table A-10 describes the implementation properties when Initiates is selected.
Table A-10 Receive Task Properties - Implementation Tab (When Initiates is Selected)
| Property | Description |
|---|---|
|
Implementation |
Enables you to determine how the receive task defines a conversation with the send task that invokes it.
|
Table A-11 describes the implementation properties when Continues is selected.
The business rules task enables you to incorporate Oracle Business Rules within your process.
See Section 6.5.2, "Introduction to the Business Rules Task" for more information.
The basic tab of the business rules task contains properties shared by multiple BPMN flow objects. See Section A.1, "Common Properties" for a list of these properties.
Table A-12 describes the properties that can be edited from the Implementation tab.
The script task is used to change values of data objects within your process
See Section 6.10.1, "Introduction to the Script Task" for more information.
The basic tab of the script task contains properties shared by multiple BPMN flow objects. See Section A.1, "Common Properties" for a list of theseS properties.
The call activity allows you to call a reusable process from within the current process.
See Section 6.4.2, "Introduction to the Call Activity" for more information.
The basic tab of the call activity contains properties shared by multiple BPMN flow objects. See Section A.1, "Common Properties" for a list of these properties.
Table A-13 describes the properties that can be edited from the Implementation tab.
Subprocesses allow you to group BPMN flow objects together to make your process more readable.
See Section 6.9.1, "Introduction to Subprocesses" for more information.
The basic tab of subprocesses contains properties shared by multiple BPMN flow objects. See Section A.1, "Common Properties" for a list of these properties.
Table A-14 describes the properties that can be edited from the Loop Characteristics tab.
Table A-15 describes the properties that can be edited from the Argument Definitions tab.
Inline handlers are types of subprocesses that allow you to model conditions that happen outside of a normal process flow.
See Section 6.9.2, "Introduction to Inline Handlers" for more information.
The basic tab of inline handlers contains properties shared by multiple BPMN flow objects. See Section A.1, "Common Properties" for a list of these properties.
The following sections describe the properties for each BPMN gateway.
The exclusive gateway enables you to split a process into two or more paths.
See Section 6.7.2, "Introduction to the Exclusive Gateway" for more information.
The basic tab of the exclusive gateway contains properties shared by multiple BPMN flow objects. See Section A.1, "Common Properties" for a list of these properties.
Table A-16 describes the properties that can be edited from the Outflows Order tab.
The inclusive gateway enables you to split your process into two or more paths.
See Section 6.7.3, "Introduction to the Inclusive Gateway" for more information.
The basic tab of the inclusive gateway contains properties shared by multiple BPMN flow objects. See Section A.1, "Common Properties" for a list of these properties.
The parallel gateway enables you to split your process into two or more paths when you want your process flow to follow all paths simultaneously.
See Section 6.7.4, "Introduction to the Parallel Gateway" for more information.
The basic tab of the parallel gateway contains properties shared by multiple BPMN flow objects. See Section A.1, "Common Properties" for a list of these properties.
The complex gateway splits a process similar to an inclusive gateway. However, it enables you to define a condition that determines if the instance can continue even if not all of the tokens have arrived at the complex gateway merge.
See Section 6.7.5, "Introduction to the Complex Gateway" for more information.
The basic tab of the complex gateway contains properties shared by multiple BPMN flow objects. See Section A.1, "Common Properties" for a list of these properties.
Table A-17 describes the properties that can be edited from the Implementation tab.
Table A-17 Complex Gateway Properties - Implementation Tab
| Property | Description |
|---|---|
|
Activation Condition |
Enables you to define a condition that specifies when the gateway releases the tokens that arrive to it. Each time a new token arrives to the complex gateway the BPMN Service Engine evaluates this condition. If the condition evaluates to true, then the complex gateway releases all the tokens that arrived until that moment. |
The even based gateway enables you to branch your process flow based on the possibility that an event may occur.
See Section 6.7.6, "Introduction to the Event-Based Gateway" for more information.
The basic tab of the event-based gateway contains properties shared by multiple BPMN flow objects. See Section A.1, "Common Properties" for a list of these properties.
The following sections describe the properties for each type of events supported by Oracle BPM.
The none start event is used when no instance trigger is specifically defined.
See Section 6.2.3, "Introduction to the None Start Event" for more information.
Table A-19 describes the properties available in the Basic tab.
Table A-19 None Start Event Properties - Basic Tab
| Property | Description |
|---|---|
|
Name |
Defines the name of this flow object. This becomes the name of the flow object within your process. |
|
Description |
Provides an optional description of this flow object. Adding a description can make your process more readable. |
The message start event triggers a process instance when a message is received.
See Section 6.2.4, "Introduction to the Message Start Event" for more information.
Table A-20 describes the properties available in the Basic tab.
Table A-20 Message Start Event Properties - Basic Tab
| Property | Description |
|---|---|
|
Name |
Defines the name of this flow object. This becomes the name of the flow object within your process. |
|
Description |
Provides an optional description of this flow object. Adding a description can make your process more readable. |
Table A-21 describes the basic properties that can be edited from the Implementation tab.
Table A-21 Message Start Properties - Implementation Tab
| Property | Description |
|---|---|
|
Type |
This property is read-only for message start events. Message start events can only initiate a conversation between two processes. |
|
Implementation |
Enables you to determine how the receive task defines a conversation with the send task that invokes it.
|
The timer start event triggers the creation of a process instance based on a specific time condition.
See Section 6.2.6, "Introduction to the Timer Start Event" for more information.
Table A-23 describes the properties that can be edited from the Implementation tab.
Table A-23 Timer Start Event Properties - Implementation Tab
| Property | Description |
|---|---|
|
Due Type |
.Determines whether the timer start event creates a process instance based on a specific date or after a specific interval has passed.
|
|
Expression Mode |
Enables you to define either the date or interval using an expression. |
The signal start event is similar to a message start event in that it is based on communication from another process or service.
See Section 6.2.5, "Introduction to the Signal Start Event" for more information.
Table A-24 describes the properties that can be edited from the Basic tab.
Table A-24 SIgnal Start Event Properties - Basic Tab
| Property | Description |
|---|---|
|
Name |
Enter a name or accept the default. This becomes the name of the flow object within your process. |
|
Description |
Provides an optional description of this flow object. Adding a description can make your process more readable. |
Table A-25 describes the properties that can be edited from the Implementation tab.
The error start event is used as the start event of an inline handler.
See Section 6.2.7, "Introduction to the Error Start Event" for more information.
Table A-27 describes the properties that can be edited from the Implementation tab.
Table A-27 Error Start Event Properties - Implementation Tab
| Property | Description |
|---|---|
|
Exception |
.Defines the error exception implemented by the error start event. This is stored in the business catalog. |
|
Catch all Business Exceptions |
Select to allow the catch event to catch any business exception. |
|
Catch all System Exceptions |
Select to allow the catch event to catch any system exception |
The none catch event is used as a place holder in your process.
The basic tab of the none catch event contains properties shared by multiple BPMN flow objects. See Section A.1, "Common Properties" for a list of these properties.
The message catch event enables you to receive a message from another process or service.
See Section 6.4.7, "Introduction to the Message Catch Event" for more information.
The basic tab of the message catch event contains properties shared by multiple BPMN flow objects. See Section A.1, "Common Properties" for a list of these properties.
Table A-28 describes basic implementation properties of the receive task.
Table A-28 Message Catch Properties - Implementation Tab
| Property | Description |
|---|---|
|
Type |
Determines how the conversation of the message catch event is implemented. A conversation defines the sequence of a group of message events that communicate with other processes or services. A message event can start a conversation with another process or service, or continue a conversation initiated by a previous message event. Possible values are:
|
Table A-29 describes the implementation properties when Initiates is selected.
Table A-29 Message Catch Properties - Implementation Tab (When Initiates is Selected)
| Property | Description |
|---|---|
|
Implementation |
Enables you to determine how the message catch event defines a conversation with the process or service that invokes it.
|
Table A-30 describes the implementation properties when Continues is selected.
Timer catch events enable you to control the flow of your process using a time condition.
See Section 6.8.2, "Introduction to the Timer Catch Event" for more information.
The basic tab of the timer catch event contains properties shared by multiple BPMN flow objects. See Section A.1, "Common Properties" for a list of these properties.
Table A-31 describes the properties that can be edited from the Implementation tab.
Table A-31 Timer Catch Event Properties - Implementation Tab
| Property | Description |
|---|---|
|
Due Type |
.Determines whether the timer catch event creates a process instance based on a specific date or after a specific interval has passed.
|
|
Expression Mode |
Enables you to define either the date or interval using an expression. |
Error catch events are intermediate events used to handle an error that occurs within your process flow.
The basic tab of the error boundary catch event contains properties shared by multiple BPMN flow objects. See Section A.1, "Common Properties" for a list of these properties.
Table A-32 describes the properties that can be edited from the Implementation tab.
Table A-32 Error Catch Event Properties - Implementation Tab
| Property | Description |
|---|---|
|
Exception |
Defines the error exception implemented by the error catch event. This is stored in the business catalog. |
|
Catch all Business Exceptions |
Select to allow the error catch event to catch any business exception. |
|
Catch all System Exceptions |
Select to allow the error catch event to catch any system exception |
The message throw event enables you to send a message to another process or service.
The basic tab of the message throw event contains properties shared by multiple BPMN flow objects. See Section A.1, "Common Properties" for a list of these properties.
Table A-33 describes basic implementation properties of the send task.
Table A-33 Message Throw Event Properties - Implementation Tab
| Property | Description |
|---|---|
|
Type |
Defines how the conversation of the message throw event is implemented. A conversation defines the sequence of a group of message events that communicate with other processes or services. A message throw event can start a conversation with another process or service, or continue a conversation initiated by a previous message event. Possible values are:
|
Table A-34 describes the implementation properties available when Initiates is selected.
Table A-34 Message Throw Event Properties - Implementation Tab (When Initiates is Selected)
| Property | Description |
|---|---|
|
Implementation |
The implementation drop-down menu enables you to determine how the send task is implemented.
|
Table A-35 describes the implementation properties when Continues is selected.
Table A-35 Message Throw Event Properties - Implementation Tab (When Continues is Selected)
| Property | Description |
|---|---|
|
Initiator Node |
Determines the message event that precedes this send task within the conversation. |
|
Inputs |
Defines the arguments required to invoke the operation the message start event exposes. |
|
Type |
Displays the process type as defined in the initiator. This property is read-only. |
|
Operation name |
Defines the name of the operation for this message catch event. Other processes and services that invoke this message catch use this operation name. |
You can use signal events to communicate a message to all the processes that are configured to wait for that message.
The basic tab of the signal throw event contains properties shared by multiple BPMN flow objects. See Section A.1, "Common Properties" for a list of these properties.
Table A-36 describes the properties that can be edited from the Implementation tab.
The none end event is used as a place holder in your process.
See Section 6.2.8, "Introduction to the None End Event" for more information on using the none end event.
The message end event is used to send a message to another process or service when the process is completed.
See Section 6.2.10, "Introduction to the Message End Event" for more information.
Table A-39 describes the properties that can be edited from the Implementation tab.
Table A-39 Message End Properties - Implementation Tab
| Property | Description |
|---|---|
|
Type |
Defines how the conversation is implemented. Since message end events can only be configured to continue a conversation, this property is read-only. |
|
Initiator Node |
Determines the message event that precedes this send task within the conversation. |
|
Inputs |
For a synchronous process, this property defines the output arguments used to invoke the operation defined by the start or catch message event. For an asynchronous, this property defines the input and output arguments required by the callback operation defined by this end event. |
|
Type |
Displays the process type as defined in the initiator. This property is read-only. |
|
Operation Name |
For an asynchronous process, this property defines the name of the operation for this message catch event. Other processes and services that invoke this message catch use this operation name. For a synchronous process, this property defines the operation of the event that precedes this end event. It can be a start or a catch event. |
You can use the signal end event to communicate a message to all the processes that are configured to wait for that message. This message communicates to these processes that the current process has finished.
Table A-41 describes the properties that can be edited from the Implementation tab.
The end error event is used when the end of a process is the result of an error condition.
See Section 6.2.9, "Introduction to the Error End Event" for more information.
Table A-43 describes the properties that can be edited from the Implementation tab.
The terminate end event is used to immediately stop a process. When a terminate end event is reached, the process stops immediately.
See Section 6.2.11, "Introduction to the Terminate End Event" for more information.
Table A-44 describes the properties that can be edited from the Basic tab.
Table A-44 Terminate End Event Properties - Basic Tab
| Property | Description |
|---|---|
|
Name |
Enter a name or accept the default. This becomes the name of the flow object within your process. |
|
Description |
Provides an optional description of this flow object. Adding a description can make your process more readable. |
Measurement marks enable you to measure a business indicator of type measure at a certain point in the process or in a section of the process. The following types of measurement marks are supported:
Start Measurement Mark
End Measurement Mark
Snapshots
Table A-45 Measurement Mark Properties
| Property | Description |
|---|---|
|
Name |
Defines the name for this measurement mark. |
|
Description |
.Provides an optional description for this measurement mark. |
|
Type |
Displays the type of measurement mark. This property is read-only. |
|
Business Indicators |
Defines the business indicators assigned to this measurement mark. See Section 7.3, "Working with Business Indicators and Counter Marks" for more information. |
.
Sequence flows define the order or sequence that work is performed within a process. The following sections describe the sequence flow properties you can edit using Oracle Business Process Composer.
Table A-46 describes the properties of default sequence flows.
Table A-46 Default Sequence Flow Properties - Basic Tab
| Property | Description |
|---|---|
|
Name |
Defines the name of this sequence flow. This name appears next to the sequence flow in your process diagram. |
|
Description |
Provides an optional description of this sequence flow. Adding a description can make your process more readable. |
Table A-47 describes the properties of default sequence flows.
Table A-47 Normal Sequence Flow Properties - Basic Tab
| Property | Description |
|---|---|
|
Name |
Defines the name of this sequence flow. This name appears next to the sequence flow in your process diagram. |
|
Description |
Provides an optional description of this sequence flow. Adding a description can make your process more readable. |
Table A-48 describes the properties of default sequence flows.
Table A-48 Conditional Sequence Flow Properties - Basic Tab
| Property | Description |
|---|---|
|
Name |
Defines the name of this sequence flow. This name appears next to the sequence flow in your process diagram. |
|
Description |
Provides an optional description of this sequence flow. Adding a description can make your process more readable. |
|
Condition |
Specifies the expression used to evaluate this conditional sequence flow. You can define an expression by clicking Edit to launch the expression editor. See Section A.3.1, "Exclusive Gateway" for more information on configuring the order in which conditional sequence flows are evaluated. |