Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com
http://www.free-online-exams.com
Problem: Problems using the iHelp designer in Sieble
Symptoms:
We're attempting to configure some iHelp items. However when we get to the design view (by drilling down on an item's name) the Java applet that lets you design the flow is locking the Siebel application.
Screenshot 1 shows you it's started the applet but nothing is displayed.
Task manager shows Siebel as 'Not Responding' & it's completely frozen the session.. I can't navigate (or do anything) in Siebel.
When I right-click on the Siebel Call Center task in the taskbar it suddenly makes the applet work. [See screenshot 2].
Each time I refresh the screen I have to go through the same procedure to make the applet work & un-freeze the Siebel application.
We have the same problem on Windows 2000 and XP machines. The version of Java we're using is JRE 1.4.2. IE is 6.0.2800.1106 on my development box. We're using the dedicated web client & are connecting to the server.
The web client and server are patched to MR 7.7.2 and this was a fresh installation (i.e. not an upgrade from 7.5) starting at 7.7.
The workflow process designer works first time and doesn't suffer from this problem.
Solution:
The customer has reported that during the process of configuring iHelp, upon navigate to the iHelp Designer View, the User experienced the Java applet locking the Siebel application.
The Task manager shows Siebel as 'Not Responding' and the application is frozen. However, when User performed a right-click on the Siebel Call Center task in the taskbar the applet works again. Each time the screen will refresh if the User perform earlier action.
During the course of research and investigation, the JRE version that customer is using is JRE 1.4.2_04 which is currently not supported as Change Request 12-LXPEOK has already been logged to address the reported behavior especially on Designer that is not supported using above version of 1.4.2_02.
The customer resolved the reported behavior by uninstall JRE 1.4.2_04 and re-install the JRE 1.4.2_02.
References:
Problems using the iHelp designer [ID 495041.1]
Symptoms:
We're attempting to configure some iHelp items. However when we get to the design view (by drilling down on an item's name) the Java applet that lets you design the flow is locking the Siebel application.
Screenshot 1 shows you it's started the applet but nothing is displayed.
Task manager shows Siebel as 'Not Responding' & it's completely frozen the session.. I can't navigate (or do anything) in Siebel.
When I right-click on the Siebel Call Center task in the taskbar it suddenly makes the applet work. [See screenshot 2].
Each time I refresh the screen I have to go through the same procedure to make the applet work & un-freeze the Siebel application.
We have the same problem on Windows 2000 and XP machines. The version of Java we're using is JRE 1.4.2. IE is 6.0.2800.1106 on my development box. We're using the dedicated web client & are connecting to the server.
The web client and server are patched to MR 7.7.2 and this was a fresh installation (i.e. not an upgrade from 7.5) starting at 7.7.
The workflow process designer works first time and doesn't suffer from this problem.
Solution:
The customer has reported that during the process of configuring iHelp, upon navigate to the iHelp Designer View, the User experienced the Java applet locking the Siebel application.
The Task manager shows Siebel as 'Not Responding' and the application is frozen. However, when User performed a right-click on the Siebel Call Center task in the taskbar the applet works again. Each time the screen will refresh if the User perform earlier action.
During the course of research and investigation, the JRE version that customer is using is JRE 1.4.2_04 which is currently not supported as Change Request 12-LXPEOK has already been logged to address the reported behavior especially on Designer that is not supported using above version of 1.4.2_02.
The customer resolved the reported behavior by uninstall JRE 1.4.2_04 and re-install the JRE 1.4.2_02.
References:
Problems using the iHelp designer [ID 495041.1]
No comments:
Post a Comment