ServiceNow Certified Application Developer - ServiceNow Training and Certification CAD Exam Questions

Answer : A

https://www.servicenow.com/community/it-service-management-forum/email-notification/m-p/695221

When configuring the content of an Email Notification, the following syntax should be used to reference the properties of an event triggering the Notification:

event..ThisisthecorrectsyntaxtoaccessthepropertiesoftheeventrecordthattriggeredtheEmailNotification,suchasevent.name,event.parm1,orevent.parm2.Forexample,{event.parm1} will display the value of the first parameter of the event.

The following syntaxes are not correct for referencing the properties of an event triggering the Notification:

current..Thisisthesyntaxtoaccessthepropertiesofthecurrentrecordthatisassociatedwiththeevent,suchascurrent.number,current.shortdescription,orcurrent.state.Forexample,{current.short_description} will display the short description of the current record.

${property name>.getDisplayValue()}. This is the syntax to access the display value of a property of the current record, such as current.state.getDisplayValue(), current.assigned_to.getDisplayValue(), or current.category.getDisplayValue(). For example, current.state.getDisplayValue() will display the state of the current record in a human-readable format, such as New, In Progress, or Closed.

${gs.}. This is the syntax to access the properties of the GlideSystem (gs) object, which provides methods for performing system operations, such as gs.now(), gs.getUserID(), or gs.getProperty(). For example, gs.now() will display the current date and time of the system. Reference: Email Notifications, Email Notification Variables

Answer : A, D

Application Access settings on a table control which operations external applications (in other scopes) can perform. The main controllable operations are:

Can create

Can read (query)

Can update

Can delete

From Development Handbook 4.0.4, p. 192:

''Application access settings determine whether another scope can read, write, create, or delete records from this table... Execute is not a valid database operation --- it pertains to script includes or other executable logic.''

Answer : C

The Allow configuration Application Access option determines whether users can configure the application tables, such as adding or modifying fields, views, or indexes. The following is true for a table with the Allow configuration option selected:

Out of scope applications can create Business Rules for the table. This is true because the Allow configuration option grants access to the table configuration to any user who has the admin or personalize_dictionary role, regardless of the application scope. This means that users can create Business Rules, which are server-side scripts that run when a record is displayed, inserted, updated, or deleted, for the table from any application.

The following are not true for a table with the Allow configuration option selected:

Only the in scope application's scripts can create Business Rules for the table. This is false because the Allow configuration option does not restrict the creation of Business Rules to the in scope application, as explained above.

Any user with the application's user role can modify the application's scripts. This is false because the Allow configuration option does not grant access to the application scripts, such as client scripts or script includes, to any user who has the application's user role. To modify the application scripts, users need to have the admin role or the application's admin role.

Out of scope applications can add new tables to the scoped application. This is false because the Allow configuration option does not allow out of scope applications to add new tables to the scoped application. To add new tables to a scoped application, users need to have the admin role or the application's admin role and be in the application scope.Reference:Application Access, Business Rules

Answer : C

While record producers are powerful tools for creating records via the Service Catalog, they cannot natively redirect users after submission. Redirection typically requires script hacks or custom widget configurations.

From ServiceNow Docs (Catalog Scripting):

''By default, record producers return the user to the catalog homepage. Redirection requires scripting using producer scripts or custom client logic.''

Answer : D

Answer : B, C

Debugging client-side scripts in ServiceNow involves utilizing tools and methods that operate within the user's browser environment, as client-side scripts execute there.

A . gs.addErrorMessage(): This function is used in server-side scripts to add error messages to the session and is not applicable for client-side debugging.

B . g_form.addInfoMessage(): This client-side function displays informational messages to the user on the form. While primarily used for user communication, it can aid in debugging by confirming the execution of certain script sections.

C . jslog(): This function logs messages to the JavaScript log, which can be viewed using browser developer tools. It's a valuable tool for debugging client-side scripts by providing runtime information.

servicenow.com

D . gs.log(): This function logs messages on the server side and is not available in client-side scripting.

Additionally, developers can use the debugger; statement within their client-side scripts. When the browser's developer tools are open, encountering this statement will pause script execution, allowing for step-by-step inspection.

Answer : D

You must script and configure all required behaviors Provided link has this statement: Extending an existing ServiceNow table means the new table inherits the parent table's columns as well as its business logic.

The following statements apply when extending an existing table:

The parent table's Access Controls are evaluated when determining access to the new table's records and fields. This is true because Access Control (ACL) rules are inherited from the parent table to the child table, unless the child table has its own ACL rules that override the parent table's rules. ACL rules are used to restrict the access to the data and functionality of the ServiceNow platform based on the user's roles and conditions.

The new table inherits the functionality built into the parent table. This is true because the new table inherits the business logic and the relationships from the parent table, such as Business Rules, Script Includes, UI Actions, UI Policies, and Reference Fields. Business logic and relationships are used to define the behavior and the structure of the data on the ServiceNow platform.

The new table inherits all of the fields from the parent table. This is true because the new table inherits the columns and the attributes from the parent table, such as Field Name, Data Type, Default Value, and Mandatory. Columns and attributes are used to define the properties and the characteristics of the data on the ServiceNow platform.

The following statement does not apply when extending an existing table:

You must script and configure all required behaviors. This is false because you do not have to script and configure all required behaviors when extending an existing table, as some of the behaviors are already inherited from the parent table, as explained above. However, you can script and configure additional or customized behaviors for the new table, such as adding new fields, creating new Business Rules, or modifying existing UI Actions.Reference:Table Extension, Access Control Rules