Siebel IP15.13 is available for download.
- IP15.13 (Patch Number: 23639315)
At the same time a new DISA release as well (to fix two in-line attachment editing defects).
- DISA 2.0.13 (Patch Number: 23596987)
On the leap day of February, IP15.9/14.15 has been released. Set aside a number of fixes, the long-awaited DISA (Desktop Integration Siebel Agent) framework has been released! And Outlook Drag-n-drop becomes reality, again.
But essentially, DISA will be a framework to support further future features, as well as allow custom-built desktop integrations. At some point.When at some point will be, is unknown at the time of writing.
Note: in the past it was communicated that the Siebel Outlook Drag-n-Drop feature (SODD) would also leverage the DISA framework. But after many considerations, the SODD feature (also part of IP15.9/14.15) will use a separate Outlook Add-in.
Reading the DISA release notes seem to imply that Incremental Repository Merge is required to take benefit of DISA. That is factually false.
Detailed instruction can be found is this fresh-from-the-press MOS Document:Oracle Support Document 2107511.1 (Install and Deploy Desktop Integration Siebel Agent (DISA)). There are just a few manual configuration steps required as the DocId mentions. More importantly, DISA does require a local client-side installation. Can be ran and provisioned as silent installer. Something to take note of, it can be obvious hurdle. There is a current limitation that the DISA installer is only available in English, but that does not affect the functionality in a multi-lingual implementation however.
Special set-up activities are required for both Firefox and Edge. The installer supports silent installation, using a response file. And DISA supports the needed security features, such as server/port white-listing and security certificates to allow secure communications.
The SODD feature will rely on a specific Outlook add-in. Now I hear you think, that will be a challenge to get across within IT. Anyways, if SODD is a looked-for feature, options are limited especially due to the NPAPI deprecation. Still on IE11? In that case you could craft your own Java-applet based solution (it has been done before).
Well, what are the the use cases supported for SODD?
All together IP15.9/14.15 is not just a patch set 🙂
Back from holidays, and happy to share that the 15.3/14.9 Patch Set nicely met the August deadline. Below the direct links to the patches. As explained these are technically identical. Although still separate downloads. Reason is that for example the IP15.1 Patch Set got packaged with (the large) dbsrvr files… And since Patch Sets are cumulative, this is something which drags along the release. Therefore the sheer size of the patch set for IP15 versus IP14.
And yes, unfortunately, tools keeps still crashing while editing eScripts as confirmed by Jason.
For those waiting, on the close of the month the Oracle Siebel development team released the combined patch set for Innovation Packs 2014 & 2015. Since code lines between IP14 and IP15 are in-sync and the applications primarily differ one and another from a repository and seed-data perspective, Oracle is able to deliver a combined patch set. Way more effective, way more efficient to develop, build, test and release. And with higher quality on top.
That said, customers coming from a prior release (IP13 or lower…) and considering to migrate should never (and I really mean never) think it’s alright migrating to anything less than Innovation Pack 2015. The traditional consideration we do not want to be the first to guinea pig a release and hence we stick with the n-1 approach is easily countered by the shared code line argument. Sure, if you uptake a new feature not available in Innovation Pack 2014 (e.g. adopting the Synergy theme for example) you could be the one spotting an early issue. But largely any framework related defects and fixes (e.g. within the object manager, industry specific features, the Open UI framework, you name it) will apply to both releases.
This link brings you to the right spot on MOS.
Patch number = 21510249.
To sum up some of the release fixes:
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.