Switching browser from IE11 to Chrome for Siebel Open UI IP15.18
12. 10. 2017
Migrating Siebel Open UI from Internet Explorer to Chrome on Windows 10 operating system with touch screen
Siebel Open UI has some higher demand on performance on the client browser side and the performance of browser is essential for a good user experience. Many enterprise siebel users may consider to migrate Siebel Open UI from traditional Internet Explorer to Chrome or Mozilla Firefox. Also the fact thatmthe Internet Explorer 11 is the last supported version from this product line rises the question, which browser will be the best fit for the Siebel Open UI application. The most common client operating system is Windows 10 and we have done our first tests using Google Chrome instead of the Internet Explorer 11 on Windows 10 Lenovo X1 Yoga Laptop with a touch display. We would like to share our findings.
It is important to point out the the Siebel Open UI migration for our client had in scope only accuracy for Microsoft Internet Explorere 11 browser. We have tested 2 verticals : Financial Services and Call Center Application. Both use CTI Toolbar for telephony and customer interactions.
As first we just typed the same url for Siebel Financial Services Application instead of in Microsoft IE11 into Chrome. The first impresion is that everything runs and renders faster. But we were supprised that the Open UI looks on the first look different. See the Picture 1 and Picture 2 you can see the comparison between IE11 and Chrome for the same applet. In the Chrome the checkboxes are sliders similiar to DJ mixing board. In the comparison Picture 3 and Picture 4 it is obvious that for list applet the controls to move forward backward for records in chrome are missing. This gave us feeling, that crhome requires a whole lot correction in order to display the same as IE11. Also the CTI Toolbar didn't react to any of the user interventions.
Picture 1 IE11 with Open UI
Picture 2 Chrome with Open UI
Picture 3 Chrome flags screen
Digging deeper we found out that the difference is mainly caused by an activated touch feature in the chrome. We found 3 ways to solve the effect,
- 1. Google Chrome enable / disable touch functions (Doc ID 2254893.1) Google Chrome automatically enables touch input if your device is equipped with a touchscreen. But if you want to limit navigation to a classic input devices (keyboard and mouse), here's how disable this feature: Open Google Chrome Type chrome://flags/ in the address bar and press Enter. Click on Enable touch events > Disabled.
- 2. OpenUI - List Applets has a New Column for Record Selection in Chrome with Windows 10 (Doc ID 2185522.1) Right-click on the Start Menu . Select Device Manager. Expand the section for Human Interface Devices. Right-click HID-compliant touch screen and choose Disable.
- 3. The third option is to customize the client javascript framework and for referenced function return false. ./siebel/decisionmanager.js:39:define("siebel/decisionmanager","3rdParty/moderniz.js",SiebelAppFacade.DecisionManager={IsTouch:function(){return Modernizr.touch} This option is favorable, if you don't want to influence laptop touch screen configuration as well as other application using chrome.
For the CTI beeing inactive in chrome with touch screen Oracle opened up a bug BUG 23110084 - SHOULD ONLY DISABLE CTI FOR THE NON-WINDOWS TOUCH DEVICES. It means in Windows 10 the CTI Toolbar after fixing this bus should always be active.
The way ahead is not clear yet. As the company uses Lenovo X1 Yoga with touch screens this becomes an issue. Disabling the touch api both in chrome and windows 10 limits the possibilities of this hardware and software. Correctly the touch mode should be active only if Windows 10 is in Tablet mode and there is no use of keyboard and mouse.
Enjoy fantastic user experience ! More coming with Siebel Open UI.
CCW Team
Späť na Blog