ServiceNow Updated CAD Exam Questions and Answers by ben

In ServiceNow, to create a module that directs users to a Record Producer (a simplified form for creating records), you should use the "URL (from Arguments)" Link Type. This configuration allows you to specify a direct link to the Record Producer.

Steps to Configure:

Navigate to Module Creation:

Go to the Application Menu where you want to add the module.

Click on "Edit Application Menu" and then "New Module."

Set Link Type:

In the module's configuration, set the Link Type to "URL (from Arguments)."

Define the URL:

In the Arguments field, provide the URL to the Record Producer. The URL typically follows this pattern:

arduino

CopyEdit

servicenow_instance_url/com.glideapp.servicecatalog_cat_item_view.do?sysparm_id=record_producer_sys_id

Replace servicenow_instance_url with your instance's URL and record_producer_sys_id with the sys_id of the Record Producer.

Explanation of Other Options:

HTML (from Arguments): Used to display custom HTML content. Not suitable for linking directly to Record Producers.

Content Page: Used to display predefined content pages within ServiceNow. Not applicable for direct Record Producer links.

Script (from Arguments): Allows execution of a script to determine the module's behavior. This is more complex and unnecessary for simply linking to a Record Producer.

Business Rule is server-side, so it uses GlideSystem API. gs.hasRoleExactly doesn't exist

In a Business Rule, the following returns true if the currently logged in user has the admin role:

gs.hasRole(‘admin’). This is the correct answer because gs is the GlideSystem object, which provides methods for performing system operations, and hasRole is a method that checks if the current user has the specified role. For example, gs.hasRole(‘admin’) will return true if the current user has the admin role, and false otherwise.

The following do not return true if the currently logged in user has the admin role in a Business Rule:

g_form.hasRoleExactly(‘admin’). This is not correct because g_form is the GlideForm object, which provides methods for manipulating forms, and hasRoleExactly is a method that checks if the current user has exactly the specified role and no other roles. For example, g_form.hasRoleExactly(‘admin’) will return true if the current user has only the admin role, and false if the current user has the admin role and any other role.

g_form.hasRole(‘admin’). This is not correct because g_form is the GlideForm object, which provides methods for manipulating forms, and hasRole is a method that checks if the current user has the specified role or any role that contains the specified role. For example, g_form.hasRole(‘admin’) will return true if the current user has the admin role or any role that contains the admin role, such as admin_ui or admin_script.

gs.hasRoleExactly(‘admin’). This is not correct because gs is the GlideSystem object, which provides methods for performing system operations, and hasRoleExactly is not a valid method of the gs object. There is no method that checks if the current user has exactly the specified role and no other roles in the gs object. References: Business Rules, GlideSystem, GlideForm

"You must first select read access to grant any other API record operation." https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/reference/r_TableApplicationAccessFields.html

The Application Access configuration fields control the access level for an application and its tables. The following Application Access configuration fields are not available if the Can read configuration field is not selected:

Can create. This field determines whether users can create records on the application tables.

Can update. This field determines whether users can update records on the application tables.

Can delete. This field determines whether users can delete records on the application tables.

These fields are not available because they depend on the Can read field, which determines whether users can view records on the application tables. If users cannot read records, they cannot create, update, or delete them either.

The following Application Access configuration fields are available regardless of the Can read configuration field:

All access to this table via web services. This field determines whether users can access the application tables using web services, such as REST or SOAP.

Allow configuration. This field determines whether users can configure the application tables, such as adding or modifying fields, views, or indexes. References: Application Access, Certified Application Developer (CAD) Learning Path

In ServiceNow, Access Controls (ACLs) are used to manage permissions for various database operations on tables and their records. The primary operations that can be controlled include:

Create:

Description: Permission to insert new records into a table.

Control: ACLs can be defined to allow or deny users the ability to create records based on roles, conditions, or scripts.

Update:

Description: Permission to modify existing records in a table.

Control: ACLs can restrict who can update records, ensuring that only authorized users can make changes.

Other Operations:

Read: Controls the ability to view records in a table.

Delete: Manages the permission to remove records from a table.

Incorrect Options:

Execute: Not a standard database operation controlled by ACLs in ServiceNow.

Query: While querying is part of the read operation, ACLs specifically control the read access rather than the query process itself.