How to set a visa service with >200 fields to be filled in HRSD?

[major li]

Hi Community,

I have a requirement of a new HR service to set up. It is about the visa application. According to the process owner, there are more than 200 fields to be filled by the applicant.

However, I am now sure if there is any OOTB function I can use. I am thinking about using catalog item cuz end user can safe as draft before submitting. in addition, I am also considering PDF documents but i will be asked to map to an COE table. Is it possible to map only limited field on the PDF and leave the rest unmapped?

Could you please share your practice please? Thank you. 

[Tanushree Maiti]

Hi @major li 

There is no OOB function/Application name Visa in place. You have to build it.

Refer: HR Service Delivery Basics Overview

HR Service Delivery 

https://www.servicenow.com/docs/r/washingtondc/employee-service-management/employee-document-managem...

https://cyntexa.com/blog/servicenow-hr-service-delivery/

Just found this which is related to Visa (not related to your requirement - it seems as it is related to FSO)

Financial Services Operations Integration with Visa 

[major li]

hi @Tanushree Maiti ,

thanks for your sharing. 

it seems that I need to create something new. May I know if you are facing with a request to ask >200 questions to the end user, how would you design this solution? 

[Tanushree Maiti · Accepted solution]

Hi @major li 

My approach for handling a form with 200 questions would be:

 

1. If users are working in Workspace

I would consider moving fulfillers to a Service Operation Workspace, which offers a modern, tab-based interface designed for efficient incident and case management. This improves usability and helps organize large amounts of information more effectively than a traditional form layout.

 

2. If all 200 questions must be presented in the Native UI or Portal

I would use a combination of the following techniques:

• Split Layout: Configure a two-column layout in the Form Designer to make better use of screen space and reduce excessive scrolling.
• Formatters and Related Lists: If groups of questions are associated with related records, I would display them through related lists or formatters rather than placing every field directly on the main form.
• UI Policies (Preferred): In most cases, displaying 200+ questions simultaneously creates a poor user experience. I would use UI Policies to dynamically show or hide fields based on user selections and responses. If necessary, Client Scripts could also be used, but UI Policies would be my preferred approach because they are easier to maintain and configure.

I have rarely encountered a requirement where all 200+ questions needed to be visible at the same time, so controlling field visibility dynamically would be a key part of the solution.