FusionGPS: Design Patterns: Guided Processes Pattern Set: Subprocess Trains

Subprocess Train

Version 2.0.0.0

Single Task Pattern Set


Description

A standalone subtask exists as a subprocess within a parent train. Subprocesses can be either be launched from within a train page (Subprocess Launched Within Page) or nested inside the train as one of its steps (Subprocess as Train Stop). The subprocess launches in the same browser window as the parent. If the subprocess is a train, it inherits properties of trains, such as the ability to be sequential or nonsequential.


Pattern Set Decision Table

	Sequential Horizontal Train	Nonsequential Horizontal Train	Two-step Guided Process	Branching Before Train	Subprocess Train
Flow through pages?	Sequential, rigid step-by-step	Nonsequential, suggested flow	Sequential from first page to second page	NA (Branch happens before train is rendered.)	Can be either sequential/ rigid or nonsequential/ suggested
Recommended number of train stops?	3-7*	3-7*	NA	NA	3-7*
Form density /amount of fields?	Medium	Medium	Medium	NA	Medium
Allows multi-user access for updating and viewing status?	No	No	No	No	No

* The number of train stops that fit on a page will vary depending on the length of the text labels. Overflow may be necessary for trains that exceed the available page width. Overflow is not recommended for novice users.


Pattern Sample

Subprocess Launched Within Page

A subprocess can be launched within a train by launching it from a button or other component within a page of the parent train.

Figure 1. A subprocess launched from a button within a train stop

Required Screen Elements
Component Type	Required Components	Customizable/Extendable Components
Train	See the appropriate Guided Process train pattern.	NA
Button/Butcon	A Button should be used to navigate the user to the drilldown subprocess train. If the user is accessing the sub-process from within a table, a butcon or menu action can also be used to perform this navigational step.	NA
Form Layout	NA	The content of the form is defined by product teams. See the Information Entry Form pattern for details

A subprocess can take several forms:

Independent Form: If the process is independent of the parent process (such as submitting a resume or any other standalone process) the final page action button is Submit. Clicking the button submits the changes then takes user back to the parent process. Title syntax follows rules for a basic form.
Two-step process: Follows rules for forms, except the syntax of the header is <subprocessname>: <step name> The parent process name is omitted.
Dialog: Follows Information Entry Form Basic Form (Dialog Box), and the title of the dialog is the name of the subprocess.
Train: See the following section

Subprocess as Train
If the subprocess takes the form of a train, clicking the Next button moves the user through the stops of the subprocess. On the last page of the subprocess, the Next button brings the user back to the same page of the parent train where the subprocess was launched.

Figure 2. The first step of a subprocess train

Required Screen Elements
Component Type	Required Components	Customizable/Extendable Components
Train	Parent Train Icon: Indicates to the user that the current train is a subprocess of another process.	Either or both parent process name and parent process step can be specified. Format of label should be: <Parent Process Name>: <Parent Process Step>

The user has completed the subprocess and can now continue to the next stop in the parent train by clicking the Next button.

Figure 3. The subprocess train has been completed and the user is returned to the parent train

Subprocess As a Train Stop

A subprocess can also be represented as a single stop on the parent train. Users access the subprocess by clicking the Next button, as if they are simply moving to the next stop in the train.

Figure 4. A subprocess in the form of a train stop

Required Screen Elements
Component Type	Required Components	Customizable/Extendable Components
Train	See the appropriate Guided Process train pattern.	NA

The user is now on the first step of the subprocess and can see the stops required to complete the subprocess before returning to the parent train. The previous and next steps of the parent train can be seen to the left and right of the subprocess train. Clicking the Cancel button will take the user out of the subprocess back into the parent train. Clicking the Next button moves the user through the stops of the subprocess. On the last page of the subprocess, the Next button takes the user to the next step of the parent train.

Figure 5. A subprocess train

Required Screen Elements
Component Type	Required Components	Customizable/Extendable Components
Train	Parent Train Icon - Indicates to the user that the current train is a sub-process of another process.	NA

The user has completed the subprocess and can now complete the next stop of the parent train.

Figure 6. The user has been returned to the parent train

Related Guidelines

Form Layout	Usage guideline for construction of forms
Header	Usage guideline for page headers, subheaders, and header syntax
Page Actions	Guidelines for page-level buttons
Save Model Guideline	Guideline for the Fusion save model
Train	Usage Guideline for the train component

About Oracle | Legal Notices | Terms of Use | Your Privacy Rights