Here are more observations from our recent upgrade to IP 2014. Continuing our list of findings in no particular order:

Theme.js No Longer Used

With IP 2014, Oracle changed the way developers register custom themes. In prior versions of Siebel, it was necessary to update a JavaScript file known as theme.js with code that registers your custom CSS. In IP 2014, this is no longer necessary. Instead, this is handled by making new entries in the Manifest Administration views. The new approach is much more straightforward and easier for Admins to administer. If you're interested, Alexander Hansal provides a great write up on how this is done at the Siebel Hub here.

Enable Open UI Parameter Automatically Updated to True

We found that after the IP 2014 upgrade scripts completed, the Enable Open UI parameter on our out of the box Object Manager had been automatically updated to True. We assume that this was because Siebel intended for all OMs to run Open UI in IP 2014. However, in our IP 2013 implementation (we performed a migration installation), we intentionally created a new, custom OM just for Open UI. This allowed us to use either HI or Open UI and compare differences between the two. We liked having the option of using both so we returned the Enable Open UI parameter to False on our out of the box OM.

Unreadable List Applet Column Headings

As mentioned in our previous post, the font size in IP 2014 has increased to 13px. This created some truncation issues for list applet columns that had previously been sized to fit a smaller font. We noticed that in IP 2014, for many of our list applets (our custom applets in particular), the list column headings/captions became unreadable because they were no longer wide enough to fit the larger text. In order to fix, we had to manually edit the HTML Width property on each of the problem list columns. This took a while and is something you should be mindful of when migrating to IP 2014. This is further illustrated in the set of print screens below. There is still some truncation in IP 2013 but it's not nearly as bad as IP 2014.

Control and List Column Display Issues with Migration Installation from IP 2013 to IP 2014

This one is hard to explain. On certain applets, we noticed that some of the list columns/controls that had been mapped to the Applet Web Template were not displaying in Open UI. We could find no clear reason as to why this was happening as everything appeared to be in order. After many attempts, we were finally able to fix the issue by deleting the list column/control mapping and then re-adding it. Again, we don't have a good explanation as to what happened but if you're migrating to IP 2014, we recommend you give yourself time to verify that you still have all of the list columns and controls you had in the prior version of Siebel.

Problems Getting Oracle Maps Integration to Work
I'm sure that by now many of you are familiar with the Oracle maps integration that comes standard on the Contacts screen in IP 2014. After we performed a migration installation from IP 2013, we noticed that the Manifest Administration entry for the Contact List Applet was referring to the siebel/custom/siebelmaprenderer.js file. This file is documented by Oracle in the Configuring Siebel Open UI: Siebel Innovation Pack 2013 which can be found with the following links:

http://docs.oracle.com/cd/E14004_01/books/config_open_ui/customizing24.html

http://docs.oracle.com/cd/E14004_01/books/config_open_ui/appendix_b_reference22.html

We checked our IP 2014 upgraded environment and could not find the siebelmaprenderer.js file and our Maps functionality was not working. We raised this issue with Oracle Support and found that the siebelmaprenderer.js file should not be used in IP 2014 without internal configuration changes. If you want to implement the Oracle maps integration then change the Manifest Administration entry to use the maprenderer.js file.

Read Only MVFs Appear Editable

After upgrading to IP 2014, we noticed that multi-value fields for read only records appear in Open UI as editable. We opened an SR with Oracle to ask why and they referenced BUG 18750311 (RWDALL MVG FIELDS IS GREYED OUT IN FORM APPLETS BUT THEY ARE ACTUALLY ENABLED). They claim that this behavior is intentional in IP 2014. This was unacceptable for our users so per Oracle Support, we added the following CSS workaround provided in Oracle Doc Id 1567865.1 to our custom theme.

.mceGridField input[readonly="readonly"],
.mceField input[readonly="readonly"]{
background:#DDD !important;
color: #727780 !important;
}

Encryption for Enterprise Server, Siebel Server and Component Password Parameters has Changed

This was touched on in one of our previous blog posts. You can find it here. After performing a migration installation from IP 2013 to IP 2014, we noticed that none of our components would start. After further research we discovered that IP 2014 uses a new encryption method for sensitive information such as passwords. Since our existing passwords were not re-encrypted with the new method, Siebel couldn't use them to perform authentication. The encryption change is referenced in the Siebel Security Guide for IP 2014:

http://docs.oracle.com/cd/E58886_01/books/Secur/Secur_ChangePwd12.html

http://docs.oracle.com/cd/E58886_01/books/Secur/Secur_DataEncrypt33.html#wp1400932

However, the guide specifically states that the re-encryption will be handled automatically. Unfortunately, this didn't happen during our upgrade so we had to do this manually. Please keep this in mind if you're moving to IP 2014.

Hope this information is helpful.

@bloomspire