Siebel Business Process Framework: Task UI Guide > Best Practices for Working with Tasks > Design Patterns for Task User Experience >
Because business components with large numbers of fields are common to Oracle's Siebel Business Applications, there are often dependencies between fields which require they be entered in a specific order. Views showing all business component fields at once are complex and difficult to use. Task UI must guide the user through the complexity in Siebel business components and the data model.
Split data entry for a single record in multiple views, typically contains a form applet based on a business component whose fields are being split. Navigating backward and forward again presents different views of the same record, with field values that have already been set being preserved.
NOTE: It is best to keep dependent fields in the same view, thus avoiding a possible deadlock, where changing a field shown in one view changes a field shown (for example, through a pick-map or the On Field Update user property) in another view and makes it irreversibly invalid.
In a task reviewing account data, relevant sub-set of Account BC's 213 single-value and 88 multi-value fields can be split in several views: first view shows identification data (Name, Location, DUNS, CSN etc.), second shows general classification info (Account Type, Industry, Territory, etc.) and third shows the communication info (primary address, phone #, fax # and URL).