ITCanopy

On : 8.2.2.4 SIA [23030] version, Configuration - General ACTUAL BEHAVIOR --------------- Next and Previous record buttons are missing on photographs applet when large image (i.e. 2000 X 1600) is used. EXPECTED BEHAVIOR ----------------------- The next and previous buttons should be visible. DETAILS ------------------- 1. What browser are you using, and what version of it? Does it happen on other browsers also (Chrome, Firefox, IE) >> Chrome, IE 2. Do you experience this on all Siebel clients (Dedicated and Web)? >> Both 3. What applet are you using? PUB Immigration Contact Photograph Form Applet. This is used to show images that are already uploaded via List Applet. PUB Immigration Contact Photograph List Applet. This is the applet which is used to upload image/photograph. >>Clones of above objects, first list applet than form applet to display the image. If I select the next image record from list applet, on form applet image is changing...

APPLIES TO: Siebel Life Sciences CRM - Version 8.1.1.9 [23016] and later Information in this document applies to any platform. SYMPTOMS In Open UI, when navigating to a view if the view takes longer that 30 seconds to load, the hourglass (Open UI busy cursor) disappears after 30 seconds, before the results are displayed. In High Interactivity, the display of the hourglass is synchronized with the total duration of the query. CAUSE By default, View loading are not expected to take longer than 30 seconds. This is configured in the Loadindicator.js file SOLUTION This behavior is addressed in the following versions: Siebel 8.1.1.11 PS16 Siebel IP2014 PS 5 Siebel IP2015 Solution 1. Launch application. 2. Go to Application - Administration > System Preferences. 3. Add the System Preference: Busy Cursor Timeout. 4. Set System Preference Value: 600 5. Save record. 6. Restart the Siebel services. 7. Test behavior.  Increase values, as needed in 30 increments. ...

BUSY CURSOR CHANGES TO POINTER BEFORE FUNCTION COMPLETES Issue: After user click on button (workflow will invoke) cursor should change to busy cursor (start showing hour glass or wait cursor icon) and until workflow completed Siebel should display busy cursor. Solution: The configuration of the view needs to be analyzed for response time tuning. If response times > 30 are acceptable the OOTB default can be changed as follow: You can modify the timeout value in Loadindicator.js. In Loadindicator.js, note that 30000 milliseconds (30 seconds) is hard coded: you can increase this value (e.g., 30000 -> 60000): var that = this; if( this.m_gbusy > 1 && config.timeOut ){ clearTimeout(this.timeoutid); this.timeoutid = setTimeout( function(){ that.timeout = true; that.Free(); }, 30000); return this; } Caution: Please keep in mind that if you implement this change you have to test and see if there is any impact on your environment. Changes/customization...

Go to Sitemap. Search for Administration - Application and click. In Aggregate view select System Preferences. create new record and set Busy Cursor Timeout for System Preference Name and set its value in seconds. all done. System Preference Name: Busy Cursor Timeout Default Value: 30 Description: Controls the maximum time the cursor shows as busy. The default value is 30 seconds and is also the minimum value. The Busy Cursor Timeout preference provides a way to customize the maximum timeout of the application based on the customer process and usage. This system preference does not change the busy cursor behavior. It provides a way to customize the hourglass timing. Busy Cursor Timeout can be interrupted by other processes that also have timeouts, such as Message Bar interval, Portlet session timeout, or any custom implementation that does a polled server call at regular intervals. The Busy Cursor Timeout value should be less than the timeout values of these process...