Guided Processes Pattern Group Version 2.0.0.0Print this Page
 
 
Description
Return to Top

The Guided Processes pattern group contains related functions or pages to guide users through complex or infrequently performed tasks. Complex transactions and multipart processes are presented in smaller and more manageable sequences of individual steps.

 
Patterns Contained in This Set
Return to Top
Activity Guides Display lengthy processes with milestones that may involve one or more roles
Checklist Page A method of displaying a task or process that contains many diverse steps (hierarchical groupings)

Single Task Pattern Set

A process guiding a single user through a single task, displayed as a series of transactional pages

 
Pattern Set Decision Table
Return to Top
 
Activity Guide Patterns
Checklist Pattern
Single Task Pattern Set
 
Length of time to complete tasks? Hours to days,
multiple sessions

Hours to days
to a single session

Single session

Number of tasks?

Ten or more in distinct groupings

Ten or more
hierarchical groupings

Single task

Number of user roles engaged in task completion?

More than one role

Single role or
multiple roles

Single role

Task organization and structure?

Milestones and submilestones
grouped into trains
and checklists

List of items or
nesting of lists

All related steps

Role collaboration?

Multiple roles

Single role
or multiple roles

None

Are tasks nested?

Two-level nesting milestones,
submilestones contain trains
and checklists

Multiple levels of
checklists supported

No

Are the task steps completed by a single user?

Not always

Not always

Yes

 
Save Model
Return to Top
Guided processes follow either a save model that caches data between steps or a save model that saves data between steps. Saving data between steps enables reentry and reentrant trains.
Cache Data Between Steps
Data is saved as a single batch upon submitting the entire set of steps from the guided process. Data is cached as the user modifies or enters data from step to step. Data for the entire set of steps is saved when the user submits the data from the last step of the guided process.

Figure 1. Caching data between steps
Save Data Between Steps
Data can be saved by clicking the Save button or the Save & Continue button to save and go on to the next step in the process. Users can roll back any saved changes by clicking the Cancel button. Saving data between steps enables re-entry and re-entrant trains. (When a save is not invoked between the steps of the process, the data is cached until an explicit save is performed.)
Figure 2 Saving data between steps
Related Patterns
Return to Top
Information Entry Forms Used in page layouts to help the user provide preformatted information, usually short (no-narrative) answers to questions
 
Related Guidelines
Return to Top
Form Layout Usage guideline for construction of forms
Header Usage guideline for page headers, subheaders, and header syntax
Save Model Guideline for the Fusion save model
Train Usage Guideline for the train component
 
About Oracle | Legal Notices | Terms of Use | Your Privacy Rights