Adding a Data Object to a Subprocess Editing a Data Object in a Subprocess

Handling Information in Your Process Design 8-11 5. Select a type. Some types allow you to define their length or decimal places.

6. Optionally, check Auto Initialize to initialize the project data object with a default

value.

7. Click OK.

8.9.2 How to Edit a Project Data Object

You can modify the name and type of an existing project data object. To edit a project data object: 1. In the BPM Project Navigator window, select a project.

2. In the Structure window, expand the Project Data Objects node.

3. Right-click the project data object you want to edit.

4. Select Edit.

A dialog to edit the project data object properties appears. 5. Make the changes you want.

6. Click OK.

8.9.3 How to Delete a Project Data Object

You can delete a project data object that you do not use or need. If there are processes in your project that use the deleted project data object, then you must remove these references manually. How to delete a project data object: 1. In the BPM Project Navigator window, select a project.

2. In the Structure windows, expand the Project Data Objects node.

3. Right-click the project data object you want to delete. A confirmation message appears.

4. Click OK.

8.9.4 How to Assign a Value to a Project Data Object

You can assign a value to a project data object using a script task. To assign a value to a project data object: 1. In the Process Editor, add a script task to the process. 2. Edit the implementation properties of the script task. Note: You cannot use the name of existing process data objects. Note: You can also add process data object from the Data Object tree in the Simple Expression Builder, XPath Expression Builder, and Data Association Dialog. 8-12 Modeling and Implementation Guide for Oracle Business Process Management 3. Define the data association or transformation to assign the value to the project data object. See Section 8.13, Introduction to Data Associations for information on how to define a data association. See Section 8.14, Introduction to Transformations for information on how to define a transformation.

8.10 Introduction to Arguments

You can use arguments to pass data between the different components in a process. A component may require you to provide certain data when you invoke it. To pass this data you use input arguments. When you run a component, it provides it results through its output arguments. The process components that may have arguments are: ■ Service Operations : may require data to process and may provide data that contains the results of running them, the input and output arguments of the component represent this data. ■ Human Tasks : may require data to run and may provide data that contains the results of running them, the input and output arguments of the Human Task represent this data. ■ Business Rules : require an input that they use to evaluate the rules they contain, they return the result of this evaluation using output arguments. When you run a Business Rule using a business rule task it uses the input and output arguments to invoke the selected decision function. ■ Message Start Events : enable you to define input arguments. You can add input arguments to a start event when a process is used as a subprocess and it receives data from the invoking process. These input arguments represent the data that a process requires when another process invokes it. ■ Message End Events : enable you to define output arguments. You can add input arguments to an end event, when a process is used as a subprocess and passes information to the process that invokes it. These output arguments represent the data that result from running the process. ■ Catch Events : allow you to define input and output arguments that define the process interface. If the operation they expose is asynchronous, then you can only define input arguments. If the operation they expose is synchronous, then you can define input and output arguments. ■ Throw Events : enable you to define input and output arguments that define the process interface.If the operation they expose is asynchronous, then you can only define output arguments. If the operation they expose is synchronous, then you can define input and output arguments.

8.11 Naming Conventions

When you name a process data object, a project data object or an argument, you should respect the following rules: ■ Use one or more nouns, or nouns modified by adjectives. ■ Do not start the name with a number.