Configuring Siebel Open UI > Post-Upgrade Configuration Tasks > About Mobile-Specific Renderers Independent of jQuery Mobile APIs >

Adapting Inheritance Hierarchies

This section includes information about changing existing customized code that was meant for mobile devices which did not have any references or calls to JQM-specific properties or methods. All such code classes should integrate into the new unified renderers with just the extension change.

To modify customized code to adapt to new unified renderers

1. Find and change class definitions:
   1. Determine if you have the following code in the beginning of your class definitions:

   if (typeof (SiebelAppFacade.CustomMobileAppletXRenderer) === "undefined") {
   SiebelJS.Namespace('SiebelAppFacade.CustomMobileAppletXRenderer');
   
   //Module with its dependencies
   define("siebel/custom/custommobileappletxrenderer", ["siebel/jqmformrenderer"], function () {
   SiebelAppFacade.CustomMobileAppletXRenderer = (function () {
   
   function CustomMobileAppletXRenderer(pm) {
   SiebelAppFacade.CustomMobileAppletXRenderer.superclass.constructor.call(this, pm);
   }
   
   SiebelJS.Extend(CustomMobileAppletXRenderer, SiebelAppFacade.JQMFormRenderer);
   .
   .
   .

   2. Replace the code found in Step a with the following code:

   if (typeof (SiebelAppFacade.CustomAppletXRenderer) === "undefined") {
   SiebelJS.Namespace('SiebelAppFacade.CustomAppletXRenderer');
   
   //Module with its dependencies
   define("siebel/custom/customappletxrenderer", ["siebel/phyrenderer"], function () {
   SiebelAppFacade.CustomAppletXRenderer = (function () {
   
   function CustomAppletXRenderer(pm) {
   SiebelAppFacade.CustomAppletXRenderer.superclass.constructor.call(this, pm);
   }
   
   SiebelJS.Extend(CustomAppletXRenderer, SiebelAppFacade.PhysicalRenderer);
   .
   .
   .

   The following definition changes are among the most important:

   • CustomMobileAppletXRenderer to CustomAppletXRenderer

     All renderers that are customized in Siebel Innovation Pack 2014 are unified renderers. They will work for all devices. This means that there will only be a singular renderer for a given applet for multiple devices. The nomenclature change is to signify that no mobile specificity exists in renderer customization.

   • ["siebel/jqmformrenderer"] to ["siebel/phyrenderer"]

     In releases prior to Siebel Innovation Pack 2014, the dependency definition section defined a jQuery Mobile oriented module or file in the call to define. These modules and files are no longer used and should be changed to modules and files in which the new extension classes are hosted.

   • SiebelAppFacade.JQMFormRenderer to SiebelAppFacade.PhysicalRenderer

     The extension hierarchy change as presented to the SiebelJS.Extend method is required because the older classes are no longer available or defined in the SiebelAppFacade namespace. Use the Table 50 as a guide to apply your modifications.

2. Determine if you have any of the following references:

   CustomMobileAppletXRenderer

3. Replace all of the references that you found in Step 2 with the following definition:

   CustomAppletXRenderer

4. Determine if you have any of the following references:

   ["siebel/jqmformrenderer"]

5. Replace all of the references that you found in Step 4 with the following definition:

   ["siebel/phyrenderer"]

6. Determine if you have any of the following references:

   SiebelAppFacade.JQMFormRenderer

7. Replace all of the references that you found in Step 6 with the following definition:

   SiebelAppFacade.PhysicalRenderer