Siebel Business Process Framework: Task UI Guide > Guidelines and Techniques for Developing a Task UI > Techniques to Improve the Usability of a Task UI >

Split View Technique

A business component record can include a large number of fields. Dependencies might exist between fields in this record that require the user to enter information in the fields in a specific order. A view that displays all business component fields simultaneously is difficult to use. A task UI can guide the user through completing these fields.

You can use a form applet that references the same business component to split data entry for a single record into multiple views. Navigating backward and forward between these views displays different fields of the same record while preserving the field values that the user enters.

It is recommended to keep fields that depend on one another in the same view. This technique avoids a problem if modifying a field value in one view causes Siebel CRM to modify a field value in another view. For example, through a pick map or the On Field Update user property.

Example of the Split View Technique

Assume a task UI includes account data that includes two hundred single value fields and eighty multivalue fields in the Account business component. This task UI uses the following views to display these account fields:

• The first view displays identification data, such as Name, Location, DUNS, and CSN.
• The second view displays classification data, such as Account Type, Industry, Territory.
• The third view displays communication data, such as Primary Address, Phone Number, Fax Number, and URL.