Siebel Database Upgrade Guide > Performing the Siebel Incremental Repository Merge > About Migrating the XML Manifest Data for Siebel Open UI from Previous Releases to the New Manifest Data in the Database >

Generic Applet Types from the XML Manifest File

Platforms: Windows, UNIX, and IBM z/OS.

This example of a generic Mobile applet shown in Figure 3 uses the AppletPR key in the XML manifest file. This key has two entries in the Object Expression view: Mobile and Desktop. The Files view contains the JavaScript file that the manifest file maps to display the applet.

Figure 3. PLATFORM Name Is Set to "IsMobileApplication()"

Figure 4 shows the entries for the navigation controls, such as ScreenPM, in the UI Objects screen.

Figure 4. Navigation Control

Figure 5 shows the entries for NAVIGATION_TREE.

Figure 5. Navigation Tree

Figure 6 shows the entries for NAVIGATION_TAB.

Figure 6. Navigation Tab

The files specified in the legacy manifest keys, RestOfUIPM and RestOfUIPR, are now located within the entries for UI Objects named PLATFORM_INDEPENDENT and PLATFORM_DEPENDENT. Figure 7 shows the migrated legacy manifest keys.

Figure 7. Legacy Manifest Keys

Files configured against a number of sections in the legacy manifest XML file are now part of these two UI Objects:

• PLATFORM DEPENDENT
• PLATFORM INDEPENDENT

Table 34 shows the mapping of the legacy XML file.

NOTE:  When processing Object Expressions Records to choose files for a given UI Object, the first Expression that evaluates to True is selected, and the file associated with it is downloaded to the browser. However, there is one exception. With the UI Object records of the Application type and Common usage type, all expressions in the Object Expression list are considered, and then they are aggregated and downloaded to the browser.