How to Edit a Process Data Object

8-8 Modeling and Implementation Guide for Oracle Business Process Management

8.6 Introduction to Subprocess Data Objects

You can define data objects for a certain subprocess. These data objects are available only when the subprocess is running. When the instance leaves the subprocess the value of subprocess data objects is lost. Using subprocess data objects is a good practice because: ■ It reduces the number of unnecessary data objects in the main process, making it simpler and easier to read. ■ By reducing the number of process data objects, it reduces the amount of memory each process instance occupies. ■ It makes the subprocess easier to understand. From within a subprocess you can access process data objects and subprocess data objects. If the name of a subprocess data object matches the name of a process data object, then when you access the data object you obtain the value of the subprocess data object.

8.7 Working with Subprocess Data Objects

You can add new project data objects to subprocesses. If necessary you can edit or delete them.

8.7.1 Adding a Data Object to a Subprocess

You can add data object to a subprocess. You can only access this data objects from within the subprocess. To add a data object to a subprocess: 1. In the BPM Project Navigator, select the process that contains the subprocess where you want to add a data object.

2. In the Structure window, expand the Activities node.

3. Expand the node that corresponds to the subprocess.

4. Right-click the Data Objects node located under the subprocess node.

5. Select New.

6. Provide a name to identify the new data object.

7. Select a type or click the Browse More Types button to select a type that is not

included in the list.

8. Optionally, check Auto Initialize to initialize the data object with a default value.

9. Click OK.

8.7.2 Editing a Data Object in a Subprocess

You can modify the name and type of an existing subprocess data object. To edit a data object in a subprocess: 1. In the BPM Project Navigator, select the process that contains the subprocess with the data object you want to edit. 2. In the Structure window, expand the Activities node. Handling Information in Your Process Design 8-9

3. In the Structure window, expand the Activities node.

4. Expand the node that corresponds to the subprocess.

5. Expand the Data Objects node located under the subprocess node.

6. Right-click the data object you want to edit.

7. Select Edit.

A dialog to edit the data object name and type appears. 8. Make the changes you want.

9. Click OK.

8.7.3 Deleting a Data Object from a Subprocess

You delete a subprocess data object that you do not need or use. If there are flow objects in your subprocess that use the removed data object, then you must remove these references manually. To delete a data object from a subprocess: 1. In the BPM Project Navigator, select the process that contains the subprocess with the data object you want to delete.

2. In the Structure window, expand the Activities node.

3. Expand the node that corresponds to the subprocess.

4. Expand the Data Objects node located under the subprocess node.

5. Right-click the data object you want to delete.

6. Select Delete.

A confirmation dialog appears.

7. Click OK.

8.8 Introduction to Project Data Objects

The processes in a BPM project often have a set of data they share. For example, the Purchase Order process and the Request Approval process may both track the value of the employee that created the request, or the priority of the request. The value of this data is different for every instance in each of those processes, they only share the necessity to keep track of that data. Project data objects allow you to ensure that all the processes in a certain project keep track of a set of data. Then each process has to assign and update the value of this data. The main benefit of defining project data objects is that after publishing your project you can configure WorkSpace views to show the values of those variables. This is only possible if you use project data objects. Another benefit is that if you change the definition of a data object, then you only have to do it one time, as opposed to having to make those changes in all the processes in the project that define the same data object.