| Bookshelf Home | Contents | Index | Search | PDF | |
Upgrade Guide for UNIX > Migrating Client Configurations > Migrating Applets and Views >
About Model Applets
The Siebel repository contains models for each type of applet and view. You should use these model objects for the Web Client migration, because model objects are designed to support diverse migration needs. For example, the model list applet has the standard Web applet buttons, Web templates, and a number of controls mapped to Web template placeholders.
Before using model applets, compare the applets you intend to migrate with the structure of the models to verify that the models suit your needs. If necessary, you can modify model applets that do not use a grid-based layout to meet your requirements. For example, you can modify models to use different Web templates, controls, or control mappings.
Before using model views, compare the views you intend to migrate with the structure of the models to verify that the models suit your needs. If necessary, you can modify model views to meet your requirements.
You may want to test the wizards against a few applets and views before running the wizards against an entire repository. To test the wizards, see Applying the Web Layout to a Set of Applets or Applying the Web Layout to a Set of Views.
Table 25 lists preconfigured model applets and views available in Release 7.x.
The Release 7.5.3 Web Client Migration wizard automatically selects a Web template based on the model applet. By default, new form applets migrate to the Web Client using a grid layout Web template.
Not all form applets can be converted to a grid layout. For version 7.5.3, an applet's class and its associated Web templates must be supported for conversion to a grid-based layout. If an applet's class is not supported, the applet migrates using a nongrid layout specified in the model form applet. Supported applet classes are defined in a configuration file called awtcvtcfg.txt, located in the binary subdirectory of the Siebel Tools installation directory.
There are two applet Web templates that support grid layout. See Table 26.
The following list summarizes how grid-based applet Web templates differ from standard applet Web templates:
- With grid-based templates, you can modify the layout of the form using Siebel Tools without having to modify the web template itself.
- With grid-based templates, labels and controls behave as separate items in the Web Layout Editor. This allows you to place them independently in the applet layout. However, labels and controls are really a single object in the repository with one set of shared properties.
- Grid-based templates do not automatically compress empty space in a column.
The wizards map items from the dedicated client layout to the Siebel Web Client using the following information from model applets and views:
- Modes to map applet Web templates. Modes determine the kind of actions available in applets to users. For example, some applets are read-only. Other applets allow users to edit data. Typical modes include: Base, Edit, and Edit List. The mode also determines which buttons appear in Web templates. For example, the Edit button appears in applets set to Edit mode, but does not appear in applets set to Base (Read Only) mode. For more information, see Siebel Tools Reference.
- Web templates to use for each mode. Templates contain placeholders for applets and are used to render Siebel views. The mode selected determines the Web template to be used. For more information about Web templates, see Siebel Tools Reference.
NOTE: For chart and tree applets, the wizard only uses the Web template information. For this reason, any applet of the appropriate type may be used as a model applet for chart and tree applets.
- Buttons that appear on migrated applets. Release 7.x Web applets typically contain additional buttons that were not used by their dedicated client predecessors. For example, the Next and Previous buttons used to scroll through record sets in the Web client did not appear in the dedicated client. During migration, the wizards automatically propagate buttons contained in the model applet so that these types of buttons do not require manual work.
- Grid-based template and applet controls. The grid layout conversion process converts a grid-based template and a set of applet controls with pixel-based coordinates into a Web-enabled layout that closely matches the original 6.x layout.
| Bookshelf Home | Contents | Index | Search | PDF | |
Upgrade Guide for UNIX Published: 20 October 2003 |