About Migrating Siebel Open UI XML Manifest Data from Previous Release to New Manifest Data in the Database

Platforms: Windows, UNIX, IBM z/OS.

In Siebel Open UI, before Siebel CRM 8.1.1.11 or 8.2.2.4, files to be downloaded for an applet were configured in one of the following ways:

Through the Applet object properties Presentation_Model and Physical_Renderer in Siebel Tools.
By adding entries under the Presentation Model and Physical Renderer sections in the manifest_extensions.map file in the SIEBSRVR_ROOT\objects folder on the Siebel Server.

The files were then configured against the key in the custom_manifest.xml file or in an application-specific custom manifest file.

Starting with Siebel CRM 8.1.1.11 and 8.2.2.4, Siebel Open UI replaces the XML manifest file with manifest data that it stores in the Siebel database, as noted in Upgrading a Custom Database Schema. You cannot modify this predefined manifest data, but you can use the Manifest Administration screen in the client to configure the manifest data that your customizations require. Applets are mapped directly to files, and expressions are configured to determine under what conditions the applets use a given file.

The following example illustrates how data from the XML manifest file is migrated. The example uses the applet Activity HI Calendar Applet, which is used for calendar functionality in Siebel Open UI. It has separate renderings in mobile and desktop applications.

Note: The migration described in this topic applies only to upgrades with custom Siebel Open UI manifest files for Siebel CRM 8.1.1.9 or 8.1.1.10, and 8.2.2.2 or 8.2.2.3.

The following figure shows the UI Objects view with two Activity HI Calendar Applet UI object entries. One of these entries has a usage type of Renderer, while the other entry has a usage type of Presentation Mode. Two object expressions are shown in the Object Expression view: Mobile and Desktop, and in the Files view, the required JavaScript file is shown.

Activity HI Calendar Applet in UI Objects View, with Object Expressions and Files: This image is described in the surrounding text.

As the following example from an earlier version shows, the two separate renderings were implemented in the XML manifest file for the applet using the CalPR key:

<PLATFORM Name="IsMobileApplication()">
  <KEY Name=SignViewPM"
  <KEY Name="SignViewPR"
  <KEY Name="AppletPR"
  <KEY Name="CalPR">
     <FILE Name>siebel/jqmcallistrenderer.js</FILE_NAME>"
  </KEY>
  <KEY Name="GridPR"
  <KEY Name="RestOfUIPR"
  </PLATFORM>
  <PLATFORM Name="IsDesktopApplication()">
  <KEY Name="AppletPR">
  <KEY Name="ListPR">
  <KEY Name="GridPR">
  <KEY Name="TaskPanePR">
  <KEY Name="TreePR">
  <KEY Name="TileRenderer">
  <KEY Name="CalPR">
     <FILE Name>siebel/jqfullcalrenderer.js</FILE_NAME>"
  </KEY>

As shown in the example, separate files for mobile and desktop platforms are configured using the CalPR key. However, for the new manifest data in the Siebel database, there are two required configured entries: Mobile and Desktop. Both expressions correspond to a single user interface object, and they are evaluated sequentially by their level number. If the setting is True for either entry, then the respective file is downloaded, and further evaluation does not take place.

However, if a record is an Application type user interface object, with a usage type of Common, then all expressions set to True are considered, not just the first in Object Expression list. All True expressions are then aggregated and downloaded to the browser. For information on modifying manifest data, see Configuring Siebel Open UI.