Process Properties

To view or edit a process's properties, double-click its diagram symbol or Browser or list entry. The property sheet tabs and fields listed here are those available by default, before any customization of the interface by you or an administrator.

The General tab contains the following properties:

Property

Description

Name/Code/Comment

Identify the object. The name should clearly convey the object's purpose to non-technical users, while the code, which is used for generating code or scripts, may be abbreviated, and should not normally include spaces. You can optionally add a comment to provide more detailed information about the object. By default the code is generated from the name by applying the naming conventions specified in the model options. To decouple name-code synchronization, click to release the = button to the right of the Code field.

Stereotype

Extends the semantics of the object. You can enter a stereotype directly in this field, or add stereotypes to the list by specifying them in an extension file.

Organization unit

Specifies the organization unit (see Organization Units (BPM)) linked to the process. You can select <Committee Process>to specify that it is realized by more than one organization unit (see Displaying a Committee Process).

Click the Properties tool beside this box to open the property sheet of the selected organization unit or the Ellipsis tool to open the list of organization units and create new ones.

Timeout

Specifies the timeout limit. The default value is zero. When the value is not set to zero, it means that a timeout exception occurs if the execution of the activation takes more than the specified timeout limit. You can type any alphanumeric value in the Timeout box (Example: 20 seconds).

Duration

Specifies estimated or statistic duration to execute the action. This property is used for documentation purposes.

Composite status

Specifies whether the process is decomposed into sub-processes. You can choose between:

  • Atomic Process (default) – the process does not contain any sub-processes.

  • Decomposed Process – the process can contain sub-processes. A Sub-Processes tab is displayed in the property sheet to list these sub-processes, and a sub-diagram is created below the process in the Browser to display them (see Decomposing Processes).

If you revert the process from Decomposed to Atomic status, then any sub-processes that you have created will be deleted.

Number ID

Specifies an incrementing number to help you identify processes. You can modify this value at any time by entering an integer greater than 0. Any change you make will not, by default, affect other numbers in the series.

When working in a data flow diagram, you can at any time right-click the diagram background and select Renumber Process IDs to renumber the processes following their position in the data flow (see Process and Data Store Numbering). Sub-processes inherit the number ID of their parent.

Keywords

Provide a way of loosely grouping objects through tagging. To enter multiple keywords, separate them with commas.

Implementation Tab

The Implementation tab lets you define how the process (activity) is implemented. Note that only decomposed processes can be implemented for the ebXML and BPEL languages: Depending on the implementation type you specify, the properties available on this tab will change. The following properties are always available.

Property

Description

Type

Specifies the type of process implementation (see Specifying Implementation Types).

[implementation object]

Depending on the implementation type you choose, an additional field or tab may be displayed, allowing you to specify a process, event, expression, operation, or data transformation upon which the implementation acts. You can use the tools to the right of the list to create an object, browse the available objects, or view the properties of the currently selected object.

Action type

[None and Reuse process implementations only] Specifies the way the process should be executed. You can choose between:
  • Manual

  • Automated

  • User-defined

[Execute operation implementation only] Specifies the type of message exchange the activity performs. You can choose between:
  • Receive request – receives a message from a partner.

  • Receive request and reply – receives a message from a partner and sends a message in response.

  • Invoke operation – initiates a message sent to a partner, the partner can respond or not.

  • Reply – sends a message to a partner in response to a received message.

  • Reply fault – sends a fault message to a partner in response to a received message.

Implementation (text box)

Specifies additional information about the process execution. You can enter any appropriate information in this box, as well as open, insert and save text files. You can open the Implementation tab by right-clicking the process symbol in the diagram, and selecting Implementation in the contextual menu.

Assignments Tab

This tab is only available for a process with the Assign implementation type, and lists the data transformations (see Data Transformations) required for the atomic assign tasks that compose the activity. An assign activity is an Xpath or XSLT expression that allows you to copy a variable value to another variable value, or to calculate the value of an expression and store it in a variable. The following properties are available:

Properties

Description

Assigned variable

Specifies the variable or organization unit [BPEL languages only] that receives the result of the transformation. Select an object from the list or click the Ellipses button to browse the available objects.

Assigned part

Specifies the message part (when the assigned variable is typed by a message format) that receives the result of the transformation. Select an object from the list.

Input variable

Specifies a source variable or organization unit (to identify the partner to whom the message is sent). Select an object from the list, or click the Ellipses button to browse the available objects.

Input part

Specifies a source message part when the input variable is typed by a message format. Select an object from the list.

The following tabs are also available: