- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2014 01:33 PM
Is it possible to set the homepage refresh default to 5 mins for ITIL users only? Ours currently defaults to Off for all new users. Changes in the setting are captured in the home_refresh preference in sys_user_preference.
Regards,
Chad
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2014 10:56 AM
Hi Chad,
Currently there is no way to set a home refresh for specific groups of users as the user preferences are user specific. (NOTE: Bharath's above suggestion does work and is set for ALL users if that is acceptable for you)
Setting home refresh can be impactful as it has the potential to expose an internal security risk in that if the user leaves their browser open on the home page, the system will never log the user out automatically.
The home_refresh value (while on the home page) bypasses the default tomcat timeout of 30 minutes or the glide.ui_session_timeout property by keeping the session active. This is documented in our wiki - https://wiki.servicenow.com/index.php?title=Modifying_Session_Timeout
There has been a new property added (as of Dublin and later) to force a session timeout even with the home_refresh value set. (Read section 3: Notes and Limitations in the above wiki).
The performance team recommends to avoid the use of the home_refresh value unless absolutely necessary and only for specific users. The home_refresh alone does not cause any noticeable overhead to the system. However, if this is implemented and the user has a poorly formatted homepage, (read - long running due to excessive gauges, reports, etc) the home_refresh will negatively impact the entire system by attempting to reload the home page at set intervals.
For instance, the home_refresh is set to 300 seconds and the homepage in question takes 40-60 seconds on average to load (a poor homepage). This is not a big deal if you have one user since this is really only about 1/5 to 1/6 of the time before the refresh runs again. However, add this homepage to 10 users and vary the times at which the homepage loads, the potential to impact the system increases exponentially as the number of users increases.
This is further documented in - https://wiki.servicenow.com/index.php?title=Customizing_Homepages
Warning: Because homepages are dynamically generated on each view, loading the homepage with too many gauges may cause performance issues throughout the instance.
Last thought - You may have users (NOC/SRE, NetEng, SysEng, etc) that have a genuine need to refresh a specific homepage on a regular interval to monitor the instance. Here is a TIP on how to run any homepage outside of the frame. This eliminates the need to load the header and sidebar which reduces the load on the instance.
1. Find homepage required to refresh often and capture sys_id
- Navigate to {instance_name}.service-now.com/sys_portal_page_list.do
- Find the homepage required for refresh (i.e. system diagnostics) right click the name and select "Copy sys_id"
- Place the sys_id in step 2 below
[optional if you cannot get to the portal page] - Go to the homepage and right click on the drop down menu "Switch to page" and select "inspect element". Expand out the page_selector and locate the sys_id of the page needed.
- EXAMPLE - <option value="776fca35210154405c9a14efc29c0aa5">Change Advisory Board Dashboard</option>
2. {instance_name}.service-now.com/home.do?sysparm_userpref_homepage={home_page_sys_id}
** Using Chrome: Install the extension "Easy Auto Refresh" to your chrome browser and set the time in seconds to automatically refresh the page.
Best Regards,
-Adam
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2014 04:35 PM
I added a value in the User Preferences table for home_refresh with a default of 300 and set the System value to true, making it a system default. Seems to be working fine so far.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2014 10:56 AM
Hi Chad,
Currently there is no way to set a home refresh for specific groups of users as the user preferences are user specific. (NOTE: Bharath's above suggestion does work and is set for ALL users if that is acceptable for you)
Setting home refresh can be impactful as it has the potential to expose an internal security risk in that if the user leaves their browser open on the home page, the system will never log the user out automatically.
The home_refresh value (while on the home page) bypasses the default tomcat timeout of 30 minutes or the glide.ui_session_timeout property by keeping the session active. This is documented in our wiki - https://wiki.servicenow.com/index.php?title=Modifying_Session_Timeout
There has been a new property added (as of Dublin and later) to force a session timeout even with the home_refresh value set. (Read section 3: Notes and Limitations in the above wiki).
The performance team recommends to avoid the use of the home_refresh value unless absolutely necessary and only for specific users. The home_refresh alone does not cause any noticeable overhead to the system. However, if this is implemented and the user has a poorly formatted homepage, (read - long running due to excessive gauges, reports, etc) the home_refresh will negatively impact the entire system by attempting to reload the home page at set intervals.
For instance, the home_refresh is set to 300 seconds and the homepage in question takes 40-60 seconds on average to load (a poor homepage). This is not a big deal if you have one user since this is really only about 1/5 to 1/6 of the time before the refresh runs again. However, add this homepage to 10 users and vary the times at which the homepage loads, the potential to impact the system increases exponentially as the number of users increases.
This is further documented in - https://wiki.servicenow.com/index.php?title=Customizing_Homepages
Warning: Because homepages are dynamically generated on each view, loading the homepage with too many gauges may cause performance issues throughout the instance.
Last thought - You may have users (NOC/SRE, NetEng, SysEng, etc) that have a genuine need to refresh a specific homepage on a regular interval to monitor the instance. Here is a TIP on how to run any homepage outside of the frame. This eliminates the need to load the header and sidebar which reduces the load on the instance.
1. Find homepage required to refresh often and capture sys_id
- Navigate to {instance_name}.service-now.com/sys_portal_page_list.do
- Find the homepage required for refresh (i.e. system diagnostics) right click the name and select "Copy sys_id"
- Place the sys_id in step 2 below
[optional if you cannot get to the portal page] - Go to the homepage and right click on the drop down menu "Switch to page" and select "inspect element". Expand out the page_selector and locate the sys_id of the page needed.
- EXAMPLE - <option value="776fca35210154405c9a14efc29c0aa5">Change Advisory Board Dashboard</option>
2. {instance_name}.service-now.com/home.do?sysparm_userpref_homepage={home_page_sys_id}
** Using Chrome: Install the extension "Easy Auto Refresh" to your chrome browser and set the time in seconds to automatically refresh the page.
Best Regards,
-Adam
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2014 03:43 PM
I totally agree with Adam. I managed to convince my customer not to go with this option. They have since reverted the setting.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-18-2017 09:40 AM
The ServiceNow Wiki content is no longer supported. Updated information about this topic is located here:
Visit http://docs.servicenow.com for the latest product documentation