Sun Web Application Guidelines - Version 4.1

Search Guidelines    |    Send Feedback   |    Developers.sun.com

How To Use These Guidelines - An Introduction
 

5 Top-Level Navigation > 5.5 Common Tasks Page > 5.5.3 Action-Based Tasks

5.5.3 Action-Based Tasks

Action-based tasks perform actions that can alter the state of the system. The required interactions can take place in a pop-up window or an inline wizard.

Examples:

• Start a Server
• Deploy an Application
• Migrate a NodeScan System for Viruses (note distinction with below)
• Adjust Virus Scanning Parameters (note distinction with above)
• Reset All Open Alarms
• Adjust Thresholds of a Disk Drive
• Create Foobar

Required

• R1 For action-based tasks, a wizard or confirmation is required. Immediate execution of the action is not allowed. See 5.5R7.
  
  
• R2 When the wizard completes or the confirmation message is shown, include an acknowledgement that the action was executed inside a results step or confirmation dialog. Feedback should include confirmation that the task was successfully completed, sufficient information about the object(s) affected, and the impact on the system (not just "<action name> done"). The user will then be navigated to the specific place in the application where the change was made. If an action does not succeed, a message stating that the action did not succeed should be included in the results step.
  
  Following is a list of sample tasks and suggestions for resulting information or forms that might be displayed to the user. In each case, the feedback is displayed in either a pop-up or wizard as described below for each type of task.
  
  
  Common Tasks and Feedback Examples
  
  

  Task	Feedback Suggestions
  Create Object	Give the object's new unique ID, initial default values of key properties, available new capacity, storage location.
  Create File	Provide the pathname, device [drive] or mount point, and machine name on which the file was created.
  Delete Object	Describe the amount of freed-up resources, any dangling references, and capacity of remaining objects.
  Move	Describe the prior and current (new) location, diminished/increased capacity at the old location and increased/diminished capacity at the new location.
  Edit Properties	Describe the effect of the new property settings (if there is anything meaningful to say) and when the new properties will take effect; i.e., immediately or upon next restart.
  Create Additional Network Route	Describe the additional and new total throughput that should be expected on the route.

  
  
  
• R3 For button labels, use action verbs to describe the task to be performed. For example, "Create Storage Volume."
  
  Note: This guideline is intentionally different from the guidelines for action buttons on object-oriented (OO) pages (for example, "New Storage Volume").
  
  
• R4 If the OO UI includes a wizard to perform a task, and there is a similar common task wizard that needs context, follow these guidelines:
  
  
  • The middle steps of the two wizards should be similar or identical (exception per R5 below). Identical steps should have identical or similar titles. The common task wizard generally would require additional steps at its beginning to solicit context from the user. Per R2 above, the common task wizard may have additional steps at the end to acknowledge the results (not needed with an OO page). Naturally, the steps are numbered differently in the two wizards. No attempt should be made to have the steps numbered similarly. Users are not going to memorize step numbers -- they will remember step contents and titles.
  • The common task wizard should NOT invoke the OO UI's actual wizard, either in sequence or as a sub-wizard (wizard steps should be reused).
    
    
• R5 The first steps to appear on the action-based task wizard should be optimized for the task at hand, not to repeat the user experience offered in the OO UI. For example, do not show the same drill-down tables shown in the OO UI. To optimize the user experience specify recognizable objects such as a unique name or a location in a hierarchy. Generally an OO UI is rich in data presentation functionality (sorting, filtering, and drill-down) to support many different use cases. With a wizard, the task is predetermined and more specific.
  
  
• R6 For search within a task wizard, place only the search fields on the page, not in a results table. This search might have one field or several depending on the application needs. When the user clicks the Next button, display the search results on the next wizard step. Above the results table, repeat the search field(s) and place a Search Again button to the right of or below them. The user can then search again on that same page, or alternatively click the Previous button to re-enter the search criteria on the previous step in the wizard sequence.
  
  Note: In the context of the task wizard described above the button label is Search Again (not just Search).

5.5.3.1 Action-Based Tasks: Flow Diagrams

Click on the links in the table below to jump to flow diagrams with more details about the interactions that take place when the user clicks on a common task.

One possibility is that there is only one object, and no further selection is needed. This may be true for a log file, or a preferences page, for example.

A second possibility is where there are multiple available objects, and the user will want to update one or more of them. The flow for such situations depends on how many objects the user will have to look through to find the object they want.

Back to Top

5 Top-Level Navigation > 5.5 Common Tasks Page > 5.5.3 Action-Based Tasks

Back to Top