Default Dashboard on Login to Next Experience

[Kieron Jones]

Hi All,

We've recently loaded Tokyo - great!

We have set the glide.next_experience.user_selected_landing_page_enabled system property to TRUE to allow users to change their landing page via their preferences.

We have also set the glide.login.home system property to $pa_dashboards, so that if the user selects "Use the Default" from their new preference option, it will show the last dashboard they accessed.

Unfortunately, when the user logs off and back on to ServiceNow, their session enters an eternal loop, not displaying the last dashboard they accessed, until the select another menu option, when that option's content is then displayed.

We have ensured that the my_home_navigation_page user preference is not present too, thinking that this may be causing conflict.  We have also noticed as a result of the loop, that the my_home_navigation_page user preference is added back in to the sys_user_preference table, but with an empty value.

The other options in the user preference (use dashboards, page where I left off, and current page) all work as expected.

What is the issue here and how can we get the user to use the default landing page / dashboard, as expected, without the loop?    As a note too, we have also set the glide.login.home to a specific dashboard, using the $pa_dashboard.do?sysparm_dashboard=ea158f3b47285114c77402f3846d4396 notation, and this still fails.

Thanks in advance of any good advice

Kieron

[Ashley Snyder]

Any response from Support yet?

You're correct in that setting glide.login.home to $pa_dashboard should be the 'Default' setting in the user selected start page settings if that's what you set the system property to.

Also I want to reply to another comment in that glide.login.home is not limited to home.do or home_splash.do?sysparm_direct=true, you can set it to $pa_dashboard.do or other pages, such as /now/nav/ui/home if you're using the landing page shipped with Next Experience UI.

[Vamsi27]

Hi Jones,

Hope you are doing well!

We are facing the same issue. Would you please let us know what was solution proposed by HI support?