Manipulating forms with GlideForm
A UI Policy conditionally performs a limited set of actions on a form, such as making a field mandatory or hiding it from view. Internally, this uses a client-side class called GlideForm, which is also available for use by the system administrator.
Just like business rules, ServiceNow provides some global variables that smooth the interaction with the platform. On every form, you'll find a g_form object.
Tip
For more information, check out the developer site: https://developer.servicenow.com/app.do#!/api_doc?v=geneva&type=client&scoped=null&to=class__client_glideform__geneva.
Using GlideForm
GlideForm provides getter and setter methods that provide access to the record as it is displayed on the screen. Let's run some code in the JavaScript executor in order to understand what options are available.
Navigate to a new Check-in record (Hotel > Check-ins, then press New). Populate the form as follows, but you don't need to save.
Room:
301(you may need...
