Configuring Siebel Open UI > Mapping Server Objects to Client Code > Configuring the Manifest File >

Example Manifest File

The following example applies a custom presentation model to a predefined list applet. It modifies the appearance and behavior of this applet so that Siebel Open UI renders it as a carousel. This example configures the rendering key for the list applet so that the presentation model uses the CarouselModel key and the physical renderer uses the CarouselRenderer key. The carouselPModel.js file is the custom presentation model that Siebel Open UI derives from the pmodel.js and listpmodel.js files.

This example assumes that carouselPModel derives from the listpmodel.js file. This configuration is necessary because a carousel displays multiple records but a form displays only a single record. Siebel Open UI derives the listpmodel.js file from the pmodel.js file. So, this configuration includes this hierarchy of derivation.

The Siebel Server returns this carouselPModel.js file when Siebel Open UI must render this applet in the client. Siebel Open UI uses the carouselPRforDesktop.js file or the carouselPRforMobile.js file that the PLATFORM_KEY_SPECIFIC section specifies, depending on if the client is a desktop computer or mobile device.

<ROOT>
...
<KEY_COMMON>
...
<KEY Name = "CarouselModel">
<FILE_NAME>pmodel.js</FILE_NAME>
<FILE_NAME>listpmodel.js</FILE_NAME>
<FILE_NAME>carouselPModel.js</FILE_NAME>
</KEY>
</KEY_COMMON>
<PLATFORM_KEY_SPECIFIC>
...
<PLATFORM Name = "Desktop">
...
<KEY Name = "CarouselRenderer">
<FILE_NAME>carouselPRforDesktop.js</FILE_NAME>
</KEY>
</PLATFORM>
<PLATFORM Name = "Mobile">
...
<KEY Name = "CarouselRenderer">
<FILE_NAME>carouselPRforMobile.js</FILE_NAME>
</KEY>
</PLATFORM>
</PLATFORM_KEY_SPECIFIC>
</ROOT>