Single component - Certain activity guide types can be defined as single component, which allows different pages from the same component to be displayed as separate steps or tasks within the activity guide. All SUOW activity guides are sequential moreover, data dependencies can be configured between steps using input/output parameters. No data is committed until a submit is performed at the final step if the user exits the activity guide before the submit, all changes are lost. Single unit of work (SUOW) - Certain activity guide types can be defined as a single unit of work spanning multiple components in the same system. It displays Next and Previous navigation buttons and some features are moved from the banner into the Actions List. Guided mode banner – Different from the standard fluid banner. Non-guided activity guides do not include any navigation buttons in addition, non-guided activity guides display the standard fluid banner. Guided - Guided activity guides include Next, Previous, and Submit (Submit can be relabeled) for navigation in the “guided mode” fluid banner. With non-sequential activity guides, tasks are not numbered and can be completed in any order unless dependencies are defined. Sequential - In a sequential activity guide, steps or tasks are numbered and must be completed in a specified order. One of the main guidelines for considering a fluid component as optimized for activity guides is that it does not make use of the left panel. Instead of presenting the steps or tasks in the left panel, a non-optimized activity guide presents a vertical dropdown list in the fluid banner (or header).Īctivity guide optimized fluid components – An activity guide-optimized fluid component adheres to the guidelines for all fluid components as well as the additional guidelines for optimized activity guide types. Non-optimized activity guides – Not recommended, support any fluid components as well as classic components. This allows an optimized activity guide to control the use and display of the left panel. Optimized - Optimized activity guides support only activity guide optimized fluid components as well as classic components. The following terms are used to differentiate the types of activity guides that can be created, and the types of processes these activity guides support: Figure 1: Example of an activity guide in Fluid Activity Guide Terminology Then, individual activity guide instances can be generated from these reusable templates.
An example is an onboarding process for a new hire that can include multiple users, and numerous tasks or steps that involve HR, Finance, Purchasing, Legal, etc.Īctivity guide templates provide a mechanism for defining the properties, security, action items, contextual data, and other options for activity guides as a onetime activity. An activity guide can also support multiple users and can be used across components. However, sometimes the user can complete the tasks in whichever order they choose, or as events dictate.
The user is presented with a series of tasks to complete a milestone. The activity guide shows users which tasks to complete and sometimes in which order. Activity guides are also optimized or non-optimized. An activity guide can be guided or non-guided, sequential or non-sequential. Activity guides track the status of your tasks or steps.Īctivity guides use the PeopleTools activity guide framework. It enables users to see exactly where they are in a process as they progress towards completion. An activity guide divides action items into a series of tasks or steps.
This documentation focuses on activity guides in Fluid applications.