Sie sind auf Seite 1von 6

Incorporate Custom Layout

INCORPORATE CUSTOM LAYOUT........................................................................................................1 ABOUT ICL:...................................................................................................................................................2 POST MERGE UTILITIES:........................................................................................................................2 PREVENTING AN OBJECT FOR ICL HANDLING: ....................................................................................................3 OBJECT TYPES THAT ARE EFFECT BY ICL: .........................................................................................................3 HOW ICL AFFECTS THE OVERALL UI:...............................................................................................................4 Screens:...................................................................................................................................................4 Views:.....................................................................................................................................................4 Applets:...................................................................................................................................................4 Deleted and Obsolete Objects:...............................................................................................................5 Web Template Files:...............................................................................................................................6

About ICL:
Incorporate Custom Layout is a Post merge utility which is executed to reduce the configuration changes to New Customer Repository after the merge. This merge utility is intended primarily to identify the UI Configuration problems prior to 7.7. ICL can be used only for upgrades from Siebel 7.x onward. ICL is intended to preserve the layout and contents of customer-modified screens, views, and applets. An ICL merge contains two extra steps. i. ii. The first step occurs at the end of the merge and applies special handling to screens, views, and applets. The second step is part of the post merge utilities and provides specialized web template files similar to the release you are upgrading from.

ICL Merge Ignores the Upgrade Ancestor Property. Standard Object uncustomized repository object and Descendant object- Modified copy of the Standard Object. The post merge utilities are implemented as a framework. Each utility in the framework is a business service and is listed in reputility.xml. Windows: SIEBEL_TOOLS_INSTALL_DIR\reppatch\reputility.xml

POST MERGE UTILITIES:


The post merge utilities are as follows: i. ii. iii. iv. v. vi. CSSGridRepPatch: Converts customized applet controls to grid-based layout. CSSUINavUpgradeReposPrep: Converts customized screens to the Siebel 7.7 UI navigation scheme. CSSMVGUpgradePatch77: Enables the shuttle feature in customized MVGs. CSSUIUpgradeReports: Lists unresolved problems in converting customized screens and views to the Siebel 7.7 UI navigation scheme. CSSWebTemplatePatch: For ICL upgrades, the utility copies Web templates into Siebel Tools that support the release you are upgrading from. CSSWFRepPatch: For workflows, this utility changes step references from rowid references to name references for child objects of steps.

In ICL Merge mode CSSGridRepPatch Utility updates (Prior 7.7) form applets copied from the Prior Customer repository are flow based but not grid based.

In ICL Merge mode CSSUINavUpgradeReposPrep Intended primarily for Prior 7.7 upgrades Screens and Views display as Follows i. ii. iii. iv. Unmodified screens with Upgrade Behavior property set to Admin display normally. Views in unmodified screens with Upgrade Behavior set to Preserve or NULL do not display. Views in customer-created screens do not display. Views added to existing screens do not display, regardless of Upgrade Behavior setting.

In an ICL merge we must review customer created, customer modified and all the views and screens where Upgrade Behavior is set to Preserve or NULL. After ICL merge mode CSSMVGUpgradePatch77 utility reconfigures MVGs as follows i. ii. Customer-created and customer-modified MVGs are not shuttle-enabled. The utility reconfigures these MVGs so they display as shuttle applets. Unmodified MVGs that have Upgrade Behavior set to Preserve or NULL are copied to the New Customer Repository during the merge and replace MVGs that are shuttle-enabled. The copied-in MVGs may not be configured as shuttle applets. The utility reconfigures the copied-in MVGs so they display as shuttle applets. Unmodified MVGs that have Upgrade Behavior set to Admin are not deactivated in the New Customer Repository and so display as shuttle applets.

iii.

Preventing an Object for ICL Handling:


There are two ways to make an object ineligible for ICL handling in the currently shipping release: i. ii. Set the Upgrade Behavior property to Non-Preservable. Set the Upgrade Behavior property to Preserve, and set ICL Upgrade Path to the currently shipping release.

Object Types that are effect by ICL:


i. Screen a. Screen View and all child objects

ii. iii. iv.

View a. View Web Template and all child objects Applet a. Applet Web Template and all child objects b. Drilldown and all child objects Screens, Views, and Applets, must be a standard object or a customer-modified object. (Customer-Created screens, views, and applets receive regular merge handling.) The object must be preservable. A screen, view, or applet is preservable if its Upgrade Behavior property is not set to Admin.

v.

How ICL Affects the Overall UI:


Screens:
The association of views with screens is preserved. For upgrades prior to Siebel 7.7, a new navigation scheme is introduced. When reviewing the UI after the merge, verify that all views can be displayed.

Views:
i. ii. iii. The association of applets with views is preserved. The layout of views is preserved. System pages such as Help, About View, About Record, and Technical Support are not preserved.

Applets:
The Web templates of standard and customer-modified applets in the Prior Customer Repository are preserved: i. When a Web template is used for an applet. Exception: for upgrades prior to Siebel 7.7, the post merge utilities provide a new Web template for MVG applets that the post merge utilities have converted to shuttle-enabled. ii. All Web template item properties are preserved: a. All control types are preserved. b. The controls that are visible are preserved. iii. No new controls from the New Siebel Repository are added or deleted. Exception: for upgrades prior to Siebel 7.7, MVG applets receive new controls as part of being shuttle enabled. iv. The location of controls in applets is preserved. v. Applet mode (whether an applet displays in more mode or less mode) is preserved. vi. Exception: for upgrades prior to Siebel 7.7, many flow-based form applets are converted to grid-based. vii. Applet Drilldowns and their child objects are preserved: a. Drilldown properties are preserved.

b. The columns that have drilldowns is preserved c. The destination views of drilldowns are preserved The following features are not preserved: i. ii. iii. Applet-level and application-level menus. Properties of controls or list columns. For example, row height, column width, caption, and popup icons are not preserved. As of Siebel 7.7, Pick and Association applets support in-line queries. This feature is implemented whether or not you choose ICL.

If you are upgrading from a Siebel 7.x release prior to Siebel 7.7, ICL has the following specific effects on applet controls and layout: i. ii. iii. Siebel 7.7 added two buttons in attachment applets: New File and New URL. An ICL merge does not add these buttons to applets. As of Siebel 7.7, MVG dialog boxes display only an OK button to close them. After an ICL merge, MVG dialog applets will have both OK and Cancel buttons. Siebel 7.7 added two new UI features, Query Assistant and Quick Print. An ICL merge does not add these buttons to applets. You must add these buttons as desired after completing the upgrade. In Siebel 7.7, applets have three default buttons: New, Delete, and Query. If you select an ICL merge, applets will keep their existing default buttons. In Siebel 7.7, the Reset button was removed from applets. If you select an ICL merge, applets keep the Reset button.

iv. v.

Deleted and Obsolete Objects:


If an object is inactive in New Siebel Repository, the object is inactive in New Customer Repository. ICL merge replaces the following object types with their counterparts from the Prior Customer Repository. The replacement object types are then set to inactive: i. ii. iii. iv. v. vi. Applet Toggle Control and child objects Drilldown and child objects List and child objects Chart and child objects Tree and child objects

Web Template Files:


The postmerge utilities make the following changes to Web template files in the Siebel Tools installation directory: i. The utilities move the Web template files for the new release from webtempl to \temp\webtempl. ii. The utilities copy Web template files from a subdirectory of reppatch\web_templates to \webtempl. These Web template files support the UI layout of the release you are upgrading from. They are similar but not identical to the Web template files included in that release. For example, if you selected the 7.5.3 and Label on Top ICL options, the post merge utilities copy Web template files from the 753 and TopLabel subdirectories of reppatch.

Das könnte Ihnen auch gefallen