As an alternative to using forms to set up and maintain task flows, you can model your task flows using Oracle Workflow (version 2.0.3.8.1 or higher) then generate a task flow. This method of creating task flows has the advantage of using a diagrammer to help you design the sequence of windows.
Note: When you create a task flow using Oracle Workflow, you must continue to maintain it using Oracle Workflow. You cannot edit a generated task flow using the Define Task Flow form.
Oracle HRMS supplies the HR Task Flow item type and a function activity for every window that can be task flowed. You model these into a workflow process for each task flow. By setting activity attributes, you create button labels and the position of buttons on each window.
There are two key rules in defining task flows:
Only certain windows are valid first windows (or top nodes) in a task flow. To check which windows are valid first windows, check the lookup types using Oracle Workflow Designer.
When you create a workflow process to model your task flow, your Start activity must connect to the Top Node Selector activity. This activity ensures that your first window is valid.
Each window in a task flow can only be connected to a window that supplies the correct context.
For example, the Position Occupancy window requires the context of a position, while the Qualifications window requires the context of a person. Each workflow activity supplied for a window has its Result Type set to a lookup type that defines the context that must be passed to it. For example, the F4 Enter Address window has the Result Type set to Person Context Windows. This means it must be given the context of a person.
Task flows are associated with one of the following contexts:
Assignment
Element Entry
Job
Location
Request for Personnel Action (US Federal HR)
People
Position Description (US Federal HR)
Position
Top node HRMS windows