Tokyo to Utah Upgrade - Homepages

[Patrick Quinlan]

Hi everyone!

We are in the process of upgrading from Tokyo to Utah and we are currently doing our testing and validation in our QA environment. One thing that we noticed in the Utah release notes is the following:

• Homepages are deprecated for upgrading customers. Homepage functionality is now found in Responsive Dashboards.

To validate this, we attempted to create a new homepage...and we were successful. 

Can anyone explain what 'Homepages are deprecated for upgrading customers' actually means? 

[SwarnadeepNandy]

Hi Patrick,

According to the product documentation, homepage deprecation means that support for homepage functionality is being phased out, and it is not possible to create or edit homepages at all when Next Experience is enabled. Next Experience is a new user interface that provides a modern and intuitive way to interact with ServiceNow applications. It is available as an opt-in feature in Utah, but it will become the default interface in future releases.

However, if you are upgrading from a previous release and you have not enabled Next Experience, you can still create and edit homepages as before. This is to allow you to migrate your existing homepages to dashboards, which are the new way of displaying data and analytics in ServiceNow. Dashboards are responsive, customizable, and interactive, and they offer many advantages over homepa....

To help you with the migration process, you can install the Homepage deprecation help tool, which is a store app that identifies all homepages on your instance and enables you to convert them to dashboards, retire them, or restore them as dashboards. You can also track the migration status and assign tasks to users and groups.

Hope this helps.

Kind Regards,

Swarnadeep Nandy

[Patrick Quinlan]

Hi Swarnadeep, 

We are upgrading from a previous release and we DO have Next Experience enabled. It was my understanding that with those two things, Homepage functionality would be limited and we would be force to migrate them to dashboards and that we would NOT be able to create new ones. 

What we've found in our QA environment, however, contradicts this. We see no difference in the behavior of Homepages (existing or the ability to create new) after upgrading to Utah. 

[Thomas_Davis]

@martapenzo can you help with understanding the concerns above?

Thanks

[martapenzo]

Hi @Patrick Quinlan ,
could you send an image of which page you are able to create new or the URL information and which is the value of the property "com.glideapp.home.deprecate_homepages".

If the property value is set to TRUE, you should not be able to create new Homepages (URL contains home.do) and you should not be able to edit the existing ones.

Thanks