Bookshelf v7.5: Implementing the User Interface

Configuration Guidelines > Configuring the User Interface >

Implementing the User Interface

After defining the screen flow and required set of user interface components, complete these steps in this order:

Configure the applets, views, screen, and application objects.

Create and modify the required controls, applet Web templates, view Web templates, and Web pages object definitions.

Compile and test the application.

Follow these guidelines to implement the user interface:

Follow the object naming conventions.

For minor changes to applets or views, reuse the existing applet or view definitions.

For major changes to applets or views, copy the existing applet or view definition, rename the applet or view, and make the appropriate modifications.

When cloning an applet, be sure to set the applet's Upgrade Ancestor property. Setting this property will make sure that any future functionality enhancements to the base applet (such as new Web templates, new Web template items, or new specialized applet class functionality) are incorporated into the cloned applet after you upgrade your application.

You can create custom HTML controls. These controls are defined in the SWF file that is contained in the application CFG file. Be aware that creating custom HTML controls requires changes in the list of values used by the Siebel repository. For more information, see Siebel Tools Reference.

Set a specific sequence for each View Web Template Item in a view. This sequence defines the order that the view applets will appear in the user interface. Also, set the view Applet Mode property on a View Web Template Item, in case the associated applet contains more than one Applet Web Template and simultaneously supports multiple modes. For example, a High Interactivity View Web Template Item could be set to the Edit List applet mode for the Account List applet, while a Standard Interactivity view using the same applet could specify the Base mode as the default mode for the same applet.

Controls that have a MethodInvoke property to go to a view or execute a SmartScript often contain user properties (for the List Column or Control definition). For examples, check in the repository.

In the Siebel Smart Web Client, SmartScript pages can be broken into several pages. This is because any question containing script must be treated as the end of a page so that the Object Manager can do any processing associated with the script before the next question is answered. For example, if a page contains three questions (q1, q2, and q3) and two of these questions have question scripts (q2 and q3), then two pages are created—one with q1 and q2 and the other with just q3. To avoid this, consider consolidating the script into the last question on the page using the Question_PreBranch or Question_Leave events. In the preceding example, question q3 would contain all of the necessary script.