Upgrades from: All Supported Siebel releases.Perform this task if you selected Incorporate Custom Layout (ICL) on your previous upgrade.

Environments: Development environment only.

Platforms: Windows, UNIX, IBM z/OS.

If you selected the Incorporate Custom Layout (ICL) merge option for your prior upgrade, then user interface objects in the New Customer Repository were deactivated and replaced by user interface objects from the Prior Customer Repository. Before upgrading to the next release, you must reactivate the standard user interface objects. You do this after the development upgrep and before the repository merge.

The migration returns the user interface to the state it would have been after a regular merge instead of an ICL merge. The following list refers to the Prior Customer Repository from your previous upgrade.

• Customer-Created screens, views and applets are retained.

• User interface controls you added in the Prior Customer Repository are retained, but control placements might need to be reconfigured.

• User interface controls, list columns, page tabs, charts, applet Web template items, and view Web template items that you deleted in the Prior Customer Repository remain deleted.

• Customer-Modified screens, views, and applets in the Prior Customer Repository that were further customized afterward are not migrated to the standard user interface. Customizations are preserved, but you might need to revise object layouts to conform to the user interface standard in the new release.

• Standard objects in the Prior Customer Repository that were not deleted, or modified afterward are migrated to the standard user interface. No reconfiguration is required.

• Standard objects in the Prior Customer Repository that were modified afterward are not migrated to the standard user interface. Customizations are preserved, but you might need to revise object layouts to conform to the user interface in the new release.

Migrating to the standard user interface uses defined logic to select objects and then modifies these objects as follows:

• ICL objects. These are the screens, views, applets and child objects that received ICL handling in your previous upgrade. The ICL merge deactivated standard user interface objects in the New Customer Repository and replaced them with ICL objects from the Prior Customer Repository. Migration to the standard user interface deactivates and deletes ICL objects and activates their counterpart standard user interface objects.

• Standard user interface objects. These are the user interface objects that were deactivated by the ICL merge step and have -UPG appended to their names. They contain customizations from the previous repository merge, such as control deletion and addition. They do not contain certain user interface layout customizations such as control placement. Migration activates these objects. Standard user interface objects replace the ICL objects for the release you are upgrading from. The layouts of some of the standard user interface objects will need to be reconfigured.