
- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 08-03-2022 10:41 AM
Problem statement - San Diego release end users may not be able to access homepages.
Solution- Please be informed in advance that from the San Diego release, support for homepage functionality is being phased out so all the homepage needs to be converted to a Dashboard. ServiceNow store has a store application called “Homepage deprecation help tool” which will help you to convert the same.
Before you use the homepage deprecation help tool, perform these two steps. A user with the admin role must change the system property. A user with the admin role or a user with both the dashboard_admin and flow_designer roles can populate the homepage migration status table.
- Disable the creation of new homepages: Set the system property com.glideapp.home.deprecate_homepages to true.
- Populate the homepage migration status table.
The Homepage deprecation help tool identifies all homepages on an instance and enables you to migrate homepages to dashboards, retire homepages, and restore retired homepages as dashboards
- As a system administration or dashboard admin, you have the ability to view a list of the homepages not yet retired or converted in your instance.
Decide what to do with them based on visibility, ownership, and usage.
Flows are triggered to convert the homepage into a dashboard or to retire the homepage and remove the visibility and editing options.
After converting the homepage to a dashboard we found that the Converted dashboard does not update the owner from a homepage so we need to update the same through a fix script.
Click on Converted Homepages on the dashboard shown below and see the owners are empty. so we need to update the same.
Script to update the same- You can use a set limit as per the volume of your homepage.
var hms = new GlideRecord('pa_homepage_migration_status');
hms .addEncodedQuery('decision=converted^owner!=NULL^dashboard.owner.nameISEMPTY');
hms .query();
while (hms .next()) {
var db= new GlideRecord('pa_dashboards');
db.get(hms .dashboard);
db.query();
if (db.next()) {
db.owner = hms .owner;
db.setWorkflow(false);
db.update();
}
}
Regards
Nayan
- 3,083 Views
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
After the San Diego Release, We couldn't be able to remove the vertical scrolling bar by Increasing/decreasing the height of the widget in the Dashboard. It is causing the issue when we export the dashboard, then table data underneath the report is buried/invisible. Any suggestions/Solutions?
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Is this only for performance analytics home page or does it relate to Non PA homepages as well?
Thanks,
Malaya
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Yes, it is for all homepages.
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
The OOB dashboard shows all the reports on PA homepages/dashboards.
How to asses the impact on non-PA dashboard.
I am not seeing any difference in the OOB Dashboard if I convert non-PA homepage into dashboard.
Any guidance here is much appreciated.
Thanks,
Malaya