Which API is used to customize the layout and behavior of forms in ServiceNow?

Which API is used to customize the layout and behavior of forms in ServiceNow?

• A. Glideform API
• B. UI Form API
• C. Form Layout API
• D. Form Customization API

Answer: (A)

Controlling how a form behaves from the browser is done with the GlideForm API. This client-side API (g_form) lets you dynamically adjust a form as the user interacts with it—showing or hiding fields, making fields mandatory or read-only, and setting or retrieving values in real time from onLoad or onChange scripts. Because of its ability to programmatically shape both layout visibility and data entry behavior directly in the form, it’s the primary tool for customizing how forms appear and function. The other options refer to aspects like how fields are arranged or labeled in the UI designer, not to a scripting API for runtime behavior, so they don’t provide the same capability to dynamically control form layout and interaction.

Controlling how a form behaves from the browser is done with the GlideForm API. This client-side API (g_form) lets you dynamically adjust a form as the user interacts with it—showing or hiding fields, making fields mandatory or read-only, and setting or retrieving values in real time from onLoad or onChange scripts. Because of its ability to programmatically shape both layout visibility and data entry behavior directly in the form, it’s the primary tool for customizing how forms appear and function.

The other options refer to aspects like how fields are arranged or labeled in the UI designer, not to a scripting API for runtime behavior, so they don’t provide the same capability to dynamically control form layout and interaction.