On June 30th Oracle released Siebel 14.7 and Siebel 15.1 Patch Sets. No co-incidence that both share the same date and release notes. From a code-line perspective they are the same.These releases just differ from a configuration and seed-data perspective.It greatly further enhances Oracle’s development agility in terms of bug fixing and quality assurance, improving reliability and time-to-market.
Don’t be afraid of the 9GB+ in size for 15.1, where 14.7 is more like the usual in size. Engineering needed to repackage the Database server files. Likely this will be optional in PS2 to reduce the size again.
That said, starting with this release, Patch Sets will also be installed using Oracle’s Universal Installer (OUI). Not a very big deal if you ask me. We still rely on oPatch for patch set verification purposes (e.g. – lsinventory) or rollback procedures.
Please check the release notes for all of the details. The Patch Set has quite a number of fixes and enhancements. To call out a couple by name:
USERS DO NOT SEE THE SPINNING WHEEL CONSTANTLY BETWEEN WHEN THEY ENTER THEIR PASSWORD AND WHEN THE APPLICATION LOADS
It addresses the issue that during logon, the spinning wheel only starts up displaying relatively late. Especially if the user’s browser cache is empty or due to static content expiration files are being downloaded again, the user might feel nothing is happening. Good UX improvement. This issue is even more important for Citrix / IE deployments (specifically IE), where typically the IE cache is not persisted between Citrix sessions, as not part of the user’s profile.
Development further improved OpenUI performance by eliminating unnecessary or expensive JQuery selectors. To name a few:
1) Ensuring that no redundant calls are being made to re-generate tabbed links for view navigation when there are no changes.
2) Ensuring that duplicate calls for modifying value in DOM element are being suppressed.
3) Reducing dependency on querySelectorAll API usage
4) Calling .empty.append for large string instead of using .html since it does regular expression check which consumes good amount of time.
5) Deferring span tag generation for iconmaps etc.