Siebel Open UI: Migrating Customizations to Innovation Pack 2013

I just upgrade to 8.1.1.11 from 8.1.1.10 with a lot of expectations and problems to be resolved. Below is my experience while migrating to Innovation Pack 2013.

Pros: Best part is that here we have a Manifest Administration View to register PM-PR files on applets. So, we will get rid of all manifest files and their uncertain problems.

Cons: I just came to know that all my customized JS files are not working in this release. Its a big setback for me.

Lets start with this problem only, we will list down changes need to be done one by one.

1.) Firstly, we will get two build folders now. And we need to put our custom files on new path, BUILD/Scripts/Siebel/Custom/. Here is BUILD is bigger version we need to use.

2.) We need to manipulate our PM-PR files to make it work on this release. Below are required changes..

1. Replace the RegisterConstructorAgainstKey method with the define method

Comment out  RegisterConstructorAgainstKey

//SiebelApp.S_App.RegisterConstructorAgainstKey(AccountGoogleMapRenderer","SiebelAppFacade.AccountGoogleMapPR" );

As of IP 2013, the concept of keys and mapping files (and manifest files) is deprecated, so we have to remove (comment out) this line of code and replace it with the define methodadd a new line like this:

define("siebel/custom/accountgooglemap_PR", [], function(){


Note that we have to set the first parameter to match the relative path to the .js file without the .js suffix.

The second parameter is an (optional) list of dependencies, so for example, a define function could look like the following:

define("siebel/custom/accountgooglemap_PR", ["siebel/phyrenderer"], function(){

This would ensure that the pre-built phyrenderer.js file is always loaded with custom file. I found that this happens even without explicitly specifying the dependency.

2. Close this define method and return

Now go to the end of the code and just before the final closing bracket ( } ) add this code:

   return "SiebelAppFacade.AccountGoogleMapPR";});


The return value of the define method is the fully qualified name (Namespace.Class) of the custom class as a string.

 
Thats all changes we need to do, and we can use remaining code as it is. 

Now we need to register PM-PR files in Manifest Administration View for required applet..
 
We will discuss Manifest Administration in our next post.
Thanks for subscribing to SimplySiebel.

Leave a Reply

Your email address will not be published. Required fields are marked *