Guidelines for Designing the Structure and Content of a Page
Use the following guidelines to design the structure of a page that displays in a task:
-
Include a title for the task that describes the goal of the task. For example: Create a New Account.
-
Include a page title that is concise. Each page title can be an explicit statement of the purpose of the page.
-
Include a page explanation. Briefly elaborate on the purpose of the page.
The following table describes the different types of content that Siebel CRM can display on a page and their recommended usage. Make sure that a page only includes content that supports the purpose of the page.
Content Type | Recommended Usage |
---|---|
Overview Page |
Displayed at the start of a task. Provides an overview of the goal of the task that can help the user to determine to proceed with the task. For example, the overview page in a driver license renewal task can indicate that completing the task requires a social security number and a driver license number. |
Step Page |
Displayed throughout a task. Includes only data that is relevant or meaningful to the current task step. |
Review Page |
Displayed before a commit step. Allows the user to review data before Siebel CRM saves it. Allows the user to review, edit, and navigate in the task to make adjustments. |
Summary Page |
Displayed at the end of a task. Provides a log and confirmation of work that the user performed. This page cannot include editable data fields because it is a confirmation of information that Siebel CRM already saved to the Siebel database. |