Defining Task Flows
You define task flows in the Define Task Flow window. If there is a similar existing task flow, you can copy it to form the basis of your new flow.
Including the Assignment Window in Taskflows
Using the combined People and Assignment form (PERWSHRG), rather than the separate forms (PERWSEPI and PERWSEMA), means the Assignment window opens more quickly from the People window.
Attention: We therefore recommend that you use the combined form in any taskflow that requires both windows. The seeded taskflows use the combined form.
When users move down a task flow from the combined form, the Assignment window remains visible in the background. They can return to the Assignment window by closing their current window. Therefore you should not define a button to call the Assignment window.
However, if you are defining a task flow to the Assignment window from any window except the People window, you should use the Assignment form (PERWSEMA). In this case you may wish to add an Assignment button to any forms below the Assignment window in the taskflow. This allows users to return to the Assignment window without going back to the top window.
Prerequisites
First create nodes for any form customizations you want to include in the task flow.
To define a task flow:
1. Enter a name for the task flow and save it.
2. In the Node block, select the name of the node that you want to be the first form in the task flow.
3. For this node, select the Top Node check box.
4. Create a new record in the Node block and select another node. You must create all the nodes for the task flow before you can begin entering the navigation paths between them.
5. In the Navigation Options region, for each node, select the other nodes to which you can navigate.
6. Enter a sequence number to determine the order in which the navigation options appear as buttons (from left to right) along the base of the window or as options in a navigation list.
7. Select the Button check box for the navigation options that should appear as buttons. There is a limit on the number of buttons that can appear on each form. This number varies from form to form.
The other options are displayed in a navigation list when the user chooses a button labelled Others. Or, if there is only one other option, this form displays when the user chooses a button labelled Next.
8. There is a default label that appears on buttons or in the navigation list for every form. You can override this with your own label.
If the label in the Define Taskflow window appears blue, this is the default value. It is a dynamic default: if the seeded value changes (for example, as the result of an upgrade), the label will be updated automatically in all task flows where it has not been overridden.
If the label appears black, the default value has been overridden. To re-inherit the default label, clear the field.
9. To define an access key (or keyboard shortcut) for a navigation option, precede the appropriate letter in the label with an ampersand (&). For example, to use ALT+P (in the Microsoft Windows environment) as the access key for the Picture window, enter the label &Picture.
Note: Do not use the following letters since they are used on the Oracle Applications menu: A, E, F, G, H, Q, S, W.
There is no validation to prevent the same letter being used more than once for a group of buttons.
To copy an existing task flow:
1. Query the existing flow and choose the Copy To button.
2. Enter the name of the new task flow and choose OK.
3. Query your new task flow and edit it as required.
See Also
Calling Customized Forms and Task Flows from Menus
