Portal Form Fields

[RakeshM89426977]

What is the use of Catalog home page and Catalog category home page fields on portal form

[Dr Atul G- LNG]

https://www.servicenow.com/docs/r/servicenow-platform/service-catalog/t_ManageCatalogPortalPages.htm.... @RakeshM89426977 

[RakeshM89426977]

Hello @Dr Atul G- LNG ,

Thanks for sharing the documentation link. I went through it, but I’m still not clear on how this answers my specific question.

Could you please explain which part of the document applies to my scenario, or share a brief example?

[Dr Atul G- LNG]

The Catalog Home Page and Catalog Category Home Page fields on the portal form are used to control how users navigate and view catalog content:

1. Catalog Home Page – This field specifies the landing page for the entire service catalog. When users access the catalog from the portal, this page is displayed first, giving an overview or featured items.

2. Catalog Category Home Page – This field specifies the landing page for a specific catalog category. When a user clicks on a category, this page is displayed first, allowing you to highlight items or information relevant to that category.

In short:

• Catalog Home Page → default entry point for the full catalog

• Catalog Category Home Page → default entry point for a specific category within the catalog

[RakeshM89426977]

Hi @Dr Atul G- LNG , thanks for the explanation. I had a follow-up based on my observations .

Initial assumption

Initially, I assumed that navigating to the Service Catalog always required clicking a specific catalog widget, where the landing page is already defined through widget instance options. Because of this, I was unclear about the actual purpose of the Catalog Home Page and Catalog Category Home Page fields on the portal record.

---

Observation

What I observed is that when creating a header menu item with the type set to Catalog, there is no need to specify a page. In this case, the system automatically redirects users to the page configured in the Catalog Home Page field on the portal form.

However, when creating a header menu item with the type set to Category, the Page field becomes visible and mandatory. The user is always redirected to the page selected in the menu item, and the Catalog Category Home Page configured on the portal is not overridden.

---

Pending doubt

Based on this behavior, my remaining doubt is:
In which scenarios is the Catalog Category Home Page field on the portal actually used, if category menu items always require an explicit page selection?