1. Business Process Framework: Task UI Guide
  2. Guidelines for Designing a Task View

Guidelines for Designing a Task View

Use the following guidelines when you design a task view:

  • Avoid redundancy. For example, avoid using multiple buttons that perform the same function. Displaying more than one button that performs the same function increases uncertainty and unnecessarily increases the complexity of the view.

  • Focus the content of the task. Configure the task to display only data that is specific to the current step. This technique helps to simplify the UI.

  • Focus feedback that the task provides. The current task pane provides feedback to the user about the progress that the user makes in a task instance. Make sure this feedback is succinct and relates only to the job task that the user is currently performing.

  • Use an applet message. If you configure the task to combine dynamic data, such as with a business component and a transient business component, then you can use an applet message. For more information, see Overview of Transient Data.

  • Use a radio button or picklist. You can configure the task to use a radio button or picklist to help the user make a decision.

  • Override default method disabling. In most situations, you must disable a default method. The following are common exceptions:

    • A New button on a list applet for nonloop operation.

    • A Query button that constrains data.

  • Avoid using a button that navigates the user to a different view. A button or a script must not navigate the user to a different view. If this situation occurs, then the task pauses. A service that calls a server component must not assume that it works on task data that Siebel CRM has not saved.

  • Avoid modifying the look and feel of a template. You typical do not need to modify a template. You can use the IsInTask, target Task UI Service (SWE) to determine whether Siebel CRM must run a section of a template only in task mode.

  • Avoid using a search specification on an applet. Instead of using a search specification on an applet, use a search specification on a task view step. This technique helps to avoid confusion if you reuse an applet across task views.

  • Use a consistent approach to page design. For example, when designing a page, do the following:

    • Begin with the page type. For example, Overview, Work, Review, or Summary.

    • Proceed with the page title.

    • Finish completing the task design.

For more information, see About the Task View.