Creating a Process (New Features in Oracle HRMS)


	Previous	Next		Contents		Library

Creating a Process

You use the Process Diagrammers within Oracle Workflow to create your task flows. You do this by adding and connecting the windows you want to appear.

You must create a top level process, sub processes are optional.

Creating a Top Level Process

You must define a top level process for each task flow. The top level process can contain sub processes, but not any other top level processes.

A top level process must have a Top Node Selector activity. This ensures that the first window in a task flow is a valid top node window. All windows that can be a top node are defined within the Top Node HRMS Context Windows lookup type.

The Top Node Selector must have two transitions. The first transition must go to the Top Node activity and its value must be the window activity name. The second transaction must be <Default> and go to the end activity.

Use the Oracle Workflow Builder to create a top level process.

To create a top level process:

1. Enter a unique internal and display name for the new process for the HR Task flow item type.

Suggestion: Use a naming convention for Internal and Display names. For example, a good internal name might be POSITION_DETAILS_TL with a Display name of Position Details (Top Level).

2. Define the process as runnable.

3. Open the Process Diagrammer window and add one Start activity and at least one End activity

4. Add a Top Node Selector activity. The Start activity must connect to the Top Node Selector activity.

5. Connect the Top Node Selector to the End activity with a <Default> transition result value.

6. Add the Top Node window.

7. Connect the Top Node Selector to the Top Node window, specifying the name of this window activity as the transition result value.

8. Connect the Top Node window to the End Activity with a <Default> transition result value.

9. Add other windows to the process, noting the following rules:

A window can only connect to another window where the Result Type is the same (such as, both Person Context windows).

The transition result value must be the name of the window activity you are connecting to (for example, F4 Enter Assignment).

Each window can only connect once to any other window.

Each window must be connected to the Top Node window with a <Default> transition result value.

You can connect a window back to its parent using the <Parent> transition result value, rather than the name of the parent window.

Creating Sub Processes

You can group a logical set of task flow windows into a sub process, which can then be used by several top level processes. This simplifies process modelling. Each sub process can contain other sub processes. There are two rules to note regarding sub processes:

A sub process cannot be defined as runnable.

When you use a sub process in another process, you must connect the sub process to the Top Node window.

To create sub processes:

1. Enter a unique internal and display name for the new process for the HR Task flow item type.

Suggestion: Use a naming convention for Internal and Display names. For example, a good Internal name might be ASSIGNMENT_DETAILS_SL with a Display name of Assignment Details (Sub Level)

2. Define the process as NOT runnable.

3. If the Sub Process requires more than one result value, specify a user defined result set as a Process Result Type.

4. Open the Process Diagrammer window and add one Start activity and at least one End activity

Because a process can have more than one result value, many End activities maybe required. At least one End Activity is required to indicate that the process must connect back to the Top Level node window.

5. Connect the Start activity to another window.

Note: The Start Activity can only connect to one window only.

6. Add other windows to the process, noting the following rules:

A window can only connect to another window where the Result Type is the same (such as, both Person Context windows).

The transition result value must be the name of the window activity you are connecting to (for example, F4 Enter Assignment).

Each window can only connect once to any other window.

Each window must connect to an End Activity with a <Default> transition result value.