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 >

Differences Between Customer Manifest Data and Oracle Manifest Data

All manifest data that replaces the previous configuration in the core_manifest.xml file is seeded in the database that is packaged with the release of Siebel CRM version. You cannot change the Oracle manifest seed data. For any UI Objects record that has been seeded in the database by Oracle, the record itself and all child Object Expression records are read-only.

If you want to customize a given UI Object, then a separate top-level UI Objects record must be created, and the required Object Expression records must be created under it. For example, if a UI Object record with a Name value of Contact List Applet is seeded in the manifest database for the Usage Type Physical Renderer, and if you want to override the configuration with a different implementation of the Physical Renderer, then you must create a new UI Objects record with a Name value of Contact List Applet and a Usage Type value of Physical Renderer, and the Object Expression record you want to create and corresponding Files record must be entered.

NOTE:  If you add a UI Objects record with the same Name, Type, and Usage Type values to a UI object that is already seeded in the Manifest database, then your newly created record is given precedence by the Manifest Runtime engine, and is used when evaluating true Object Expression values when choosing a File record to download. There is one exception, however. For UI Objects records with a Type value of Application and a Usage Type value of Common, both the Oracle seeded record and your new record are considered. The sum total of all the chosen Files for both the seeded record and your new record is aggregated and downloaded to the browser.