Default Landing Page loading before custom landing page

[Jewell_Aubert]

The default landing page appears to be loading before my custom landing page.  So the tab shown in the screenshot attached shows the default, then it will eventually load the custom.  Is there a way to bypass this so that the default doesn't show at all?  We cannot make any changes to the default to prevent this from happening because of the protection policy.  Just wondering if there was a work around.

[VarunS]

Hi @Jewell_Aubert ,

This is a known behavior in ServiceNow workspaces (particularly Employee Center / HRSD). The default landing page briefly flashes before your custom landing page loads because the workspace initially renders the out-of-box (OOB) default page, and then the configuration for your custom page kicks in and redirects or replaces it.

Here are a few approaches you can try to resolve or minimize this:

1. Set your custom page as the default landing page in the Workspace configuration:

- Navigate to sys_aw_workspace.list and open your HRSD workspace record.

- In the "Landing Page" field, set it to your custom landing page instead of the OOB default.

- This ensures the workspace loads your custom page directly rather than loading the default first and then switching.

2. Use a UX App Route or App Shell configuration:

- If you are using Employee Center Pro or a Workspace built on the Next Experience UI Framework, you can configure the default route to point to your custom page. Check the UX App Routes (sys_ux_app_route) table and ensure your custom landing page is set as the default route for the workspace.

3. Clone and customize instead of creating net-new:

- Rather than creating a completely separate custom landing page, consider cloning the default landing page variant and customizing it. This way the workspace loads your customized version of the default page directly, avoiding the flash of the OOB page.

4. Check the Page Variant configuration:

- Navigate to the Landing Page variants (Workspace Experience > Pages > Landing Page) and ensure your custom variant has the correct audience/conditions set AND that it has a higher order/priority than the default variant. If the default variant evaluates first, it will briefly render before your custom variant takes over.

Since you mentioned you cannot modify the default due to protection policy, option 1 (changing the workspace landing page setting) or option 4 (ensuring your custom variant has higher priority) are likely your best paths forward. These approaches configure the workspace to load your custom page first rather than modifying the protected default page.

Hope this helps!