UI Policies are the primary tool for conditionally showing or hiding form elements, including buttons, based on user roles, field values, or other criteria. Checking this first directly addresses the most common cause for a missing UI element in a role-specific context.

Access Control Rules (ACLs) are the fundamental and most secure method for controlling record-level access in ServiceNow. Configuring an ACL on the sc_cat_item table to require the user’s department is ‘Finance’ for read access ensures the item does not appear in the catalog for unauthorized users at the data level.

The core distinction is where they execute. Business Rules are server-side scripts triggered by database operations (insert, update, delete, query). Client Scripts are client-side (browser) scripts that enhance form behavior, like field validation, display, or dynamic changes, without requiring a server trip.

A Scheduled Report allows you to define filter conditions (priority=high, state=open, created before last 48 hours), choose a format (like list), set a schedule (e.g., daily at 8 AM), and distribute it via email or store it. This creates an automated, reusable solution that delivers the required data without manual intervention.

UI Policies are the declarative, low-code method for conditionally making fields mandatory, read-only, or visible/invisible based on field values. They are easier to configure, maintain, and understand than scripted alternatives for this common form behavior requirement.

To create a related list from Table B (License) on a form for Table A (User), you must first establish the relationship. This is done by adding a reference field (like ‘Assigned to’ or ‘User’) on the License table that points to the User record. Once this relationship exists, you can add the ‘Licenses’ related list to the User form via Form Layout.

A ‘before’ Business Rule that runs on ‘Insert’ is the correct server-side mechanism for setting a field’s value automatically when a record is first created. It can access the ‘caller’ reference field and its ‘name’ attribute (current.caller.name) and concatenate it into the ‘short_description’ field before the record is saved to the database.

Assignment Rules are designed specifically for this purpose. They can be configured to watch for a condition (e.g., Assignment group changes to ‘Network’) and then automatically perform multiple actions, such as changing the assignment group to a more specific one (‘Network Support’) and setting other field values like Category.

Roles control data access (via ACLs), while Modules control navigation (what appears in the application menu). A user must have a role that is associated with a module to see that module. If the ‘asset’ role exists but is not associated with any module in the menu, the user will not see the Asset application, even though they have the role.

UI Policies are the primary tool for conditionally showing or hiding form elements, including buttons, based on user roles, field values, or other criteria. Checking this first directly addresses the most common cause for a missing UI element in a role-specific context.0