HRSD Record Producer

[PREETI RANA]

Hi Community,

I have a requirement in an HR Onboarding catalog item that contains around 250 variables. Displaying all of them on a single page affects the user experience.

I want to split the form into multiple pages on the Service Portal, displaying approximately 50 variables per page, with Next and Previous buttons to navigate between sections until the user reaches the final page and submits the request.

Has anyone implemented a similar solution? What would be the best approach to achieve this in ServiceNow while keeping it as a single catalog item/record producer?

Any guidance or recommended approach would be greatly appreciated. Thank you!

[DavidW447091066]

Yes, it's possible. Use variable sets or containers with client scripts/UI Policies to show one section at a time and navigate with Next/Previous buttons, while keeping everything in a single catalog item. If you're using Service Portal, a custom widget can make the wizard experience much smoother.

[Tanushree Maiti]

Hi @PREETI RANA 

OOB Servicenow does not provide these feature.

Workaround:

Option 1:  If the HR Onboarding process has distinct phases (like General Info, Equipment, Software, Access), break it down into multiple smaller catalog items tied to an Order Guide. 

Option2: Using Container Start/End with approximately 50 variables per container and dynamically controlling visibility through Catalog UI Policies or Catalog Client Scripts is the preferred solution.

If containers are not used, structure the form into logical sections and use UI Policies or client scripts to progressively reveal variables so the form remains usable and the user experience is not negatively impacted.

[yashkamde]

Hello @PREETI RANA ,

Refer this might help :

Multi Page Catalog Items 

Service Catalog Item Wizard in Service Portal 

If my response helped mark as helpful  and accept the solution.

[Vikram Reddy]

Hi @PREETI RANA,

Skip the native Break variable type for this, it's a documented known error for record producers on Service Portal, and Container Start/End inside a Variable Set has its own layout bug there too. What actually holds up at 250 variables is a custom Service Portal widget that treats each Variable Set as a page.

1. Group the 250 variables into 5 Variable Sets of roughly 50, ordered logically
2. Build a widget that toggles set visibility via the GlideForm client API behind your own Next and Previous buttons
3. Submit the underlying record producer only on the final page, it's still one catalog item under the hood, so approvals and flow logic stay untouched
4. Keep onLoad catalog client scripts lean, a 58-variable form was reported taking around 90 seconds to load when scripts ran synchronous calls

Want me to sketch the widget's show/hide logic, or is grouping the variable sets the part you're stuck on?

Thank you,
Vikram Karety
Octigo Solutions INC