Action History and Participant List Version 2.0.0.0Print this Page
Notifications and Approvals Pattern Group
 
Description
Return to Top

The action history displays how a task is routed through the participants in a workflow. Action history includes steps already performed by the participants as well as future steps in the routing of the task. The action history pattern is used in the History section of task detail pages.

The participant list is used to preview the routing of a human task before it is initiated. This pattern is typically embedded in flows that kick off a workflow task. For example, the participant list is used to preview the list of approvers before an expense report or a requisition is submitted.

The SOA Task History component is used to implement both of the action history and participant list patterns. The SOA Task History compoent is available in both tabular and graphical representations.

 
Pattern Samples
Return to Top

Action History: Tabular

Displays the task action history in tabular format (view only and editable). Content includes past, current and future participants.

Action History: Graphical

Displays the task action history in graphical format (view only). Content includes past, current and future participants.
Participant List: Tabular Displays the list of future tasks participants in tabular format (view only and editable). Use this list before the task is launched to show a preview of who will be involved in the routing.
Participant List: Graphical Displays the list of future tasks participants in graphical format (view only). Use this list before the task is launched to show a preview of who will be involved in the routing.
 
Action History: Tabular Format
Return to Top

The action history component displays the action history from beginning to end. Content includes all steps in the workflow, including steps that are complete and steps that are pending. The action history table can be view-only or editable. The SOA Task History component includes the ability to view a snapshot of the task and attachments at various points in the workflow.

History, simple version
Figure 1. Tabular action history table example
Required Screen Elements
Component Type Required Components Customizable or Extendable Components
Toolbar (optional)  
  • Editing controls (optional)
    • Add
    • Edit
    • Delete
    • Reset
  • View Snapshot (optional): Displays a snapshot of the state of the task as seen by the end user at that point in time.
  • Future Participants: Enables the user to include or exclude future participants.
  • Full task actions checkbox: The default state is to have this control deselected. Enables the users to include or exclude tasks that do not make changes to the task, such as adding comments.
Table columns

Contains the following columns:

  • Sequence (column title hidden): Numbering of each discrete action taken on the request. Note that parallel items get assigned the same number.
  • Participant: Person or system component assigned to an action. Linked to a dialog box with more details about the person.
  • Action: Action taken
  • Action Date

 

 

 
Action History: Graphical Format
Return to Top

The action history table, in graphical format, displays the action list and process flow in an easy-to-scan graphical format.

 
Graphical view
Figure 2. Graphical action history example
Required Screen Elements
Component Type Required Components Customizable or Extendable Components
Participant boxes

Contains the following information:

  • Participant: Person or system component assigned to an action
  • Status icon button: Indicates the current status of the task
 
 
Participant List (View Only and Editable)
Return to Top

The participant list is used to display the list of participants before a task is submitted. For example, the participant list is used to display the list of people who must approve a purchase requisition or an expense report before the user submits the task. This table can be view-only or editable.

List Editing
The participant list enables end users (given the right permissions) to edit the contents of the list. Actions are taken by selecting a row and then clicking the desired icon button from the table toolbar. Reset does not require a selection.

As part of a task flow, the end user may need to modify the approval list that is presented by the system. For example, during the creation of a requisition in Oracle Procurement, the preparer or requester can preview as well as modify the approval list prior to submitting the requisition.
Given the right permissions, the user can:

  • Add a participant: Users can insert ad-hoc approvers to the generated approval list. The user can select the location to insert the ad-hoc approvers. For example, a preparer can add additional approvers needed to approve the requisition. Participants can also be added with view-only privileges. For example, a preparer can add a viewer when the preparer needs to inform a person of business purchases and decisions, without requiring a response.
  • Remove a participant: If allowed, a user can remove system-generated approvers and viewers. Ad-hoc approvers and viewers can always be removed.
  • Reset: Reset has two options: Reset and Reset to Default. Reset removes changes made since the last save. Reset to Default reverts the approval list back to the original system-generated approval list.
History, simple version
Figure 3. Participant list, tabular example
Participant List: Graphical (View Only)
Return to Top

The participant list displays the list of participants and a process flow in an easy-to-scan graphical format.

History, simple version
Figure 4. Participant list, graphical example
Required Screen Elements
Component Type Required Components Customizable or Extendable Components
Participant boxes

Participant: Person or system component assigned to an action

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