Contextual Container Pool Version 2.0.0.0Print this Page
Pooling Pattern Set
 
Description
Return to Top

The Contextual Container Pool pattern provides for the compact and persistent appearance of the pooled items throughout the application, such as a shopping cart or the document builder. The Contextual Container Pool pattern is appropriate for when users need to see the pooled content and add to it as they perform actions in the main content region. The pooled content can be stored for an extended period of time so that the pool can serve as a reminder to users of the objects that they have already collected.

Due to the limited vertical space in the contextual area, this pattern displays only the items most recently added to the pool. This pattern may be used in conjunction with the Page Pooling pattern, which displays the full list of pooled items.
 
Pattern Set Decision Table
Return to Top
  

Contextual
Container Pool

Shuttle Pool

Page Pool
Should the pooled content appear persistently? Yes No No
Does the user need to see all of the selected items at one time? No Yes Yes
Is iterative searching required? Yes Yes No
Is compact presentation of the pooled objects required? Yes No No
Is the pooled content maintained over sessions? Yes No Yes
Does the user need to edit the contents of the pooled container? No Yes Yes
Does the user need to see the recently added item in the context of the complete list of pooled items? No Yes Yes
 
Pattern Sample
Return to Top
Example A: Shopping Cart
The contextual pooling container appears in the contextual pane of the framework. The user can perform any actions in the content region, and the pooling container remains visible as long as the pane is open. The user can hide the contextual container by collapsing the accordion section or collapsing the entire contextual pane.
Figure 1. The shopping cart and the contextual container
Required Screen Elements
Component Type Required Components Customizable or Extendable Components
Accordion Panel This panel should be located in the Contextual Area pane. NA
Accordion Pane Title The title should reflect the purpose and type of objects that apppear in the pool (for example, Shopping Cart or Item Comparison). NA
Text

If the pooling container does not contain the full list of items added, indicate the total number of items that has been added.

Use this format: Your <pooling container> contains <number of object> items

For example: Your cart contains 0 items

NA
Button

Add to <pooling container>: Adds the object to the pool. Label the button so that the link between the button and the pooling container is clear (for example, Add to Cart).

Selecting the button should update the pooling container contents to reflect the added item.

Quantity (text field): Product teams can include this field if more than one unit of each object can be added.

Button: Use a button to add an item to a pool. You can use either a text button or an icon button. Icon buttons are appropriate for row action columns or toolbars, while text buttons are more appropriate for novice users.

The added object appears in the contextual content object (accordion pane). As more objects are added to the container, only the most recently added objects appear in the container. Older items are removed from view. The user can view the total list of added objects by clicking a button (View Cart, in this example). The user will be navigated to a page that displays the complete list of pooled items, which is detailed in the Page Pooling pattern.
Figure 2. Only the most recently added objects appear in the Shopping Cart container
Required Screen Elements
Component Type Required Components Customizable or Extendable Components
Accordion Panel This panel should be located in the Contextual Area pane. NA
Accordion Pane Title The title should reflect the purpose and type of objects that appear in the pool (for example, Shopping Cart or Item Comparison). NA
Accordion Panel
  • Indicate the total number of items that has been added

    Use this format: Your <pooling container> contains <number of object> items

    For example: Your cart contains 0 items

  • The Recently Added Items section lists the last n objects that have been added to the cart, where n is defined by product teams.

    To ensure the panel remains compact, it is recommended that n be set to 4 or less.
 NA
Accordion Panel Buttons
  • A View <pooling container> (for example, View Cart) button: Enables the user to view the full list of items in the pool. This button is optional if the pool contains all of the added items.
  • An action button (for example, Compare, Checkout): Navigates the user to the task flow for which the pooled items will be evaluated or used.

Product teams can choose not to use the View <pooling container> button if the pooling panel is designed to render the full list of items added.

A button to add an item to a pool can be a text button or an icon button. Icon buttons are appropriate for row action columns or toolbars, while text buttons are more appropriate for novice users.
Example B: Document Builder
The document builder is another example of the contextual pooling container that is more common in business applications. The document builder provides advanced functionality to the contextual container and is appropriate for skilled users.
Figure 3. The document builder
Required Screen Elements
Component Type Required Components Customizable or Extendable Components
Accordion Panel This panel should be located in the Contextual Area pane. NA
Accordion Pane Title The title should reflect the purpose and type of objects that appear in the pool (for example, Document Builder or Item Comparison). NA
Accordion Panel
  • Use a one-column layout for label and data elements.
  • Indicate the total number of items that has been added.

    Use this format: Number of <Object Type>: <objects in the pool> (for example: Number of Lines: 5).
NA
Accordion Panel Buttons
  • View <pooling container> (for example, View Cart): Enables the user to view the full list of items in the pool. This button is optional if the pool contains all of the added items.
  • Save button: Saves the contents of the cart.
  • Action button (for example, Compare, Checkout): Navigates the user to the task flow for which the pooled items will be evaluated or used.
 Product teams can choose not to use the View <pooling container> button if the pooling panel is designed to render the full list of items added.
Toolbar Button Add to <pooling container>: Adds the object to the pool. Label the button so that the link between the button and the pooling container is clear (for example, Add to Document Builder).

Clicking the button should update the pooling container contents to reflect the added item. 		NA
The pooled content can be saved for future use or acted upon (in this example, clicking the Create button generates a new purchase order.
Figure 4. Pooled content for viewing or acting upon
 
Related Guidelines
Return to Top
Accordion Guidelines for content panels in the regional area
Page Layout Guidelines for the regions of the page
Page Actions Guidance on page-level actions
Page Layout Guidelines for the regions of the page
UI Shell Guidance about the user interface (UI) shell and the contextual pane
Table Guidelines for the table component
 
About Oracle | Legal Notices | Terms of Use | Your Privacy Rights