Practice Free CAD Certified Application Developer - ServiceNow Exam Questions Answers With Explanation

In ServiceNow, the Caller Access field is used to define the level of access that external scripts or applications have to a particular script include or application resource. The valid options for the Caller Access field are:

None: No special restrictions are applied; the resource is accessible as defined by other security settings.

Caller Restriction: Limits access to the resource, allowing only specified callers or applications to invoke it.

Caller Tracking: Enables tracking of which callers are accessing the resource, providing an audit trail for monitoring purposes.

Options such as "Accessible from," "Allow Configuration," and "Caller Permission" are not valid selections for the Caller Access field.

For more detailed information, refer to the official ServiceNow documentation on Restricted Caller Access Privileges.

https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/task/t_IncludeApplicationData.html

https://developer.servicenow.com/dev.do#!/learn/courses/tokyo/app_store_learnv2_flowdesigner_tokyo_flow_designer/app_store_learnv2_flowdesigner_tokyo_notifications_in_flow_designer/app_store_learnv2_flowdesigner_tokyo_inbound_email_and_flows

"By default, the system generates a watermark label at the bottom of each notification email to allow matching incoming email to existing records." https://docs.servicenow.com/bundle/tokyo-servicenow-platform/page/administer/notification/concept/c_WorkingWithWatermarks.html

In ServiceNow, the Application Picker is a user interface element that allows developers to select the active application they are working on. The selected application determines the Application Scope, which defines the boundaries within which application artifacts (like tables, scripts, and UI components) reside and operate.

A. Selecting Global in the Application Picker sets the Application Scope to Incident: This is incorrect. Selecting "Global" sets the scope to the global application, not specifically to the Incident application.

B. Global is a reserved application that does not appear in the Application Picker: This is incorrect. The "Global" application is available in the Application Picker and represents the global scope.

C. Selecting an application from the Application Picker sets the Application Scope: This is correct. Choosing an application from the Application Picker establishes that application's scope as the current context for development and configuration.

D. Selecting an application from the Application Picker does not set the Application Scope: This is incorrect. The Application Picker directly influences the current Application Scope.

For more information, refer to the official ServiceNow documentation on Application Scope.

For a visual demonstration of restricting access to your ServiceNow application, you may find the following video helpful:

Restricting Access to your ServiceNow App

It is possible to change an application’s scope in ServiceNow, either from global to private or from private to global. However, changing the scope of an application may affect its functionality and compatibility with other applications. Therefore, it is recommended to test the application thoroughly before and after changing its scope.

How To Change Application Scope In ServiceNow - YouTube

How to move Custom Scoped Applications bettween instances - ServiceNow

Steps to switch a scoped application from your company’s application repository to update sets - ServiceNow

How to change the application (scope) of a SLA Definition without needing to recreate the SLA Definition - ServiceNow

Advantages of Scoped Applications in ServiceNow - QualityClouds

 The application development plan is a document that outlines the scope, objectives, deliverables, and timeline of a software project1. It should include the following business requirements and processes:

Data input/output: This describes what data is needed for the application to function, how the data is collected, stored, processed, and displayed, and what outputs are generated by the application2.

Business problem: This defines the problem or opportunity that the application aims to address, the current situation, the desired outcome, and the benefits of the solution3.

Process steps: This details the steps involved in the application development lifecycle, such as planning, designing, testing, deploying, and maintaining the application4.

Users/stakeholders: This identifies the people who will use, benefit from, or influence the application, their roles, responsibilities, and expectations, and how they will be involved in the project5.

References = 1: Application Development Lifecycle: Phases, Steps and Process3 2: Tips for Writing Business Requirements Documents2 3: Business Requirements Document Template: 7 Components1 4: Requirements Development Steps4 5: What is Business Process Documentation?: 10 Easy Steps to5

Application Access settings in ServiceNow control which operations are permitted on a table by other applications. The following operations can be restricted:

Query (A) - Valid: Controls whether other applications can read (query) records from the table.

Create (B) - Valid: Determines whether other applications can add new records to the table.

Execute (C) - Incorrect: No such operation exists for Application Access.

Update (D) - Incorrect: "Update" permissions are controlled through Access Control Lists (ACLs), not Application Access settings.

An application admin is a role that grants full access to an application and its tables, scripts, and other components1. An application admin can create, modify, and delete any element of the application, as well as publish and install it2. An application typically has an application admin role that is automatically created and assigned to the application creator3.

References = 1: Application administration - ServiceNow Docs 2: Application admin role - ServiceNow Docs 3: Application roles - ServiceNow Docs

https://docs.servicenow.com/bundle/tokyo-application-development/page/build/guided-app-creator/concept/guided-app-creator.html

Flow Designer is a no-code platform capability that lets you automate business processes in a single drag-and-drop design environment. Some of the features of Flow Designer are:

Add stages to a flow: You can define the stages of a flow to track its progress and status. Stages can be used to group actions, subflows, and conditions into logical units.

Call a flow from another flow or subflow: You can reuse existing flows or subflows by calling them from another flow or subflow. This allows you to modularize your automation and avoid duplication of logic.

Test a flow using the “Run as” feature: You can test a flow using the “Run as” feature to specify the user context and input parameters for the flow execution. This helps you to verify the functionality and performance of your flow before publishing it.

Flow Designer – No-Code Workflows - ServiceNow

Flow Designer - ServiceNow

Flow Designer Data Sheet - ServiceNow

Inbound Action scripts are server-side scripts that run when an email is received by the system. They can use the current object to access the record that is created or updated by the email, and the email object to access the properties and methods of the email message. The previous and event objects are not available in Inbound Action scripts. The producer object is only available in Record Producer scripts, which are used to create records from a service catalog item.

 When configuring a REST Message, the Endpoint is:

The URI of the data to be accessed, queried, or modified. This is the correct answer because the Endpoint is the part of the REST Message that specifies the location and the resource of the REST provider. The Endpoint is composed of the base URL and the resource path, which can include query parameters or variables. For example, the Endpoint for a REST Message that retrieves the weather information for a city from a web service could be https://api.openweathermap.org/data/2.5/weather?q=London.

The following are not correct definitions of the Endpoint when configuring a REST Message:

The commands to the REST script to stop execution. This is not correct because the commands to the REST script to stop execution are not part of the REST Message, but of the Scripted REST API, which is a feature that allows users to create custom REST endpoints on the ServiceNow platform. The commands to the REST script to stop execution are methods of the RESTAPIResponse object, such as setStatusCode, setError, or complete.

Information about the format of the returned data. This is not correct because the information about the format of the returned data is not part of the Endpoint, but of the HTTP headers or the Accept field of the REST Message. The HTTP headers or the Accept field can be used to specify the content type of the response, such as JSON, XML, or HTML.

The response from the provider indicating there is no data to send back. This is not correct because the response from the provider indicating there is no data to send back is not part of the Endpoint, but of the HTTP status code or the response body of the REST Message. The HTTP status code or the response body can be used to indicate the result of the REST request, such as 200 OK, 404 Not Found, or 500 Internal Server Error. References: REST Messages, Scripted REST APIs

In ServiceNow, the "Allow access to this table via web services" option within the Application Access settings determines whether the table can be accessed through web service protocols, such as REST and SOAP. When this option is selected, it permits the table to be accessible via web services; however, it does not override existing permissions. The user or system making the web service request must still have the appropriate permissions (such as roles and access controls) to perform operations on the table's records.

Option A: Incorrect. If the "Allow access to this table via web services" option is not selected, the table is not accessible via web services, regardless of user permissions.

Option B: Correct. Enabling this option allows the table to be accessed via web services, but the user must have the correct permissions to access the table's records.

Option C: Incorrect. This option applies to all web service protocols, including both SOAP and REST.

Option D: Incorrect. This option controls overall web service access to the table; specific operations (create, read, update, delete) are governed by user permissions and access controls.

An example of when an application might not use a Scheduled Script Execution (Scheduled Job) is when the application needs to run a client-side script at the same time every day. A Scheduled Script Execution is a server-side script that runs on a specified schedule and performs some action on the server or database. A client-side script runs on the user’s browser and cannot be scheduled by ServiceNow. The other options are examples of when an application might use a Scheduled Script Execution, such as sending email reminders, running a clean up script, or querying the database for unassigned records. Reference: Scheduled Script Execution, Client scripts

"A table that extends another table is called a child class, and the table it extends is the parent class" - this is about halfway down in this link below: https://docs.servicenow.com/en-US/bundle/tokyo-platform-administration/page/administer/table-administration/concept/table-extension-and-classes.html

Access Control scripts are server-side scripts that run when an Access Control rule is evaluated. They can use the gs and current objects to access the GlideSystem and GlideRecord methods, respectively. Some of the useful methods in Access Control scripts are:

gs.hasRole() - This method checks if the current user has a specified role. It returns true if the user has the role, and false otherwise. For example, gs.hasRole(‘admin’) will return true if the user is an administrator, and false otherwise.

current.isNewRecord() - This method checks if the current record is a new record that has not been inserted into the database yet. It returns true if the record is new, and false otherwise. For example, current.isNewRecord() will return true if the record is being created, and false if the record is being updated or deleted.

The methods g_user.hasRole() and current.isNew() are not part of the server-side scripting API. They are part of the client-side scripting API, which is used in Client Scripts and UI Policies. They cannot be used in Access Control scripts.

Configuring the label of a field in a child table changes the label only on that table, not on the base table or the parent table. The base table is the table that contains the common fields for all the extended tables, and the parent table is the table that is directly extended by the child table. The label of a field on the base table or the parent table can be different from the label on the child table. References: [ServiceNow Docs - Table extension], [ServiceNow Community - How to change field label in child table]

From: https://docs.servicenow.com/bundle/paris-application-development/page/script/general-scripting/reference/r_ScriptingAlertInfoAndErrorMsgs.html

g_form.showFieldMsg("field_name", "Hello World", "error"); Puts "Hello World" in an error message **below the specified field**. g_form.addInfoMessage() or g_form.addErrorMessage() place a blue box message at the top of the screen. Pg 126 of the CAD handbook

The method that prints a message on a blue background to the top of the current form by default is g_form.addInfoMessage(). The g_form object is a global object that provides access to form fields and UI elements on a form. The addInfoMessage() method is a method of the g_form object that displays an informational message next to the form header. The message has a blue background color by default, unless it is overridden by a CSS style. The addInfoMessage() method takes one argument, which is the message text to display. References: [ServiceNow Docs - GlideForm (g_form) API], [ServiceNow Docs - g_form.addInfoMessage()]

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.

"Application developers must select an application as their current scope context." https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/task/t_SelectAnAppFromTheAppPicker.html

The fastest way to create and configure a Record Producer is to open the table in the Table records and select the Add to Service Catalog Related Link. This will automatically create a Record Producer with the same fields as the table and add it to the Service Catalog. You can then modify the Record Producer as needed. The other options require more steps and manual configuration. Reference: Create a record producer

In ServiceNow, Application Files are configuration records that define the various components and logic that constitute an application. These include artifacts such as:

Business Rules

Client Scripts

UI Actions

Script Includes

Tables and Fields

Workflows

These artifacts collectively define the functionality and behavior of the application. When an application is developed, ServiceNow automatically creates and manages these Application Files to represent the application's components.

Option C is correct because Application Files are the fundamental building blocks that comprise a ServiceNow application, representing its various components and configurations.

Options A, B, and D are incorrect:

A: XML exports of an Update Set represent changes made to an instance but are not synonymous with Application Files.

B: CSV files are typically used for data import/export and do not represent the configuration components of an application.

D: An XML export of table records pertains to data within a table, not the configuration artifacts that define application behavior.

ServiceNow provides several methods to install applications onto an instance, each suited to different scenarios:

Import an Application from an XML File (Option A):

Description: Developers can export an application as an XML file and then import it into another ServiceNow instance.

Use Case: This method is commonly used for moving applications between instances, such as from development to production.

Procedure:

Navigate to "System Applications" > "Applications."

Click on the "Import" button.

Upload the XML file of the application.

"Schema map: Provides a graphical representation of the relationships between tables."

https://docs.servicenow.com/bundle/tokyo-platform-administration/page/administer/table-administration/concept/c_TableAdministration.html

The elements of an Access Control are evaluated in the following order: Conditions, Roles, Script. The Conditions are a set of criteria that must be met for the Access Control to apply. The Roles are a list of user roles that are required to access the object. The Script is an optional script that can further restrict or allow access based on custom logic. If any of these elements return false, the Access Control denies access and stops evaluating the remaining elements. Reference: Access control rules

there are only two types of UX options: Mobile and Classic. Classic is defined as "manage records via lists and form"

When designing and creating a form, you can create sections to organize fields on a form. Sections are containers that group related fields together and provide a label and a description for the group. You can use sections to improve the readability and usability of the form. You can also collapse or expand sections to show or hide the fields within them.

The other options are not valid ways to organize fields on a form. Related lists are not fields, but lists of records that are related to the current record on the form. Tabs are not part of the form, but part of the application menu that allows you to navigate between different modules. Buttons are not fields, but elements that perform actions on the form, such as saving, updating, or deleting the record.

Global applications can use Automated Test Framework and Flow Designer features, but not Source Control and Delegated Development features. Source Control and Delegated Development features are only available to scoped applications . References: [Global vs Scoped Applications], [Delegated Development]

The server-side API debug log method available for scoped applications is gs.info(). This method logs informational messages that describe the progress of the application. Older methods such as gs.print() and gs.log() are not available in scoped applications. The gs.debuglog() method does not exist. The gs.info(), gs.warn(), gs.error(), and gs.debug() methods work in both scoped applications and global, and are therefore more versatile going forward in future versions. Reference: Debugging best practices

The Event Registry is a table that stores the definitions of all the Events that can be triggered or processed by the ServiceNow system1. The Event Registry allows ServiceNow to react when Events are generated by executing actions such as sending notifications, running scripts, or starting workflows2. The Event Registry also provides information about the Event parameters, description, and source3.

References = 1: Event Registry - ServiceNow Docs 2: Event Management - ServiceNow Docs 3: Event Registry form - ServiceNow Docs

https://developer.servicenow.com/dev.do#!/learn/courses/tokyo/app_store_learnv2_scripting_tokyo_scripting_in_servicenow/app_store_learnv2_scripting_tokyo_server_side_scripting/app_store_learnv2_scripting_tokyo_script_includes

In ServiceNow, a Record Producer is a specific type of catalog item that enables users to create task-based records through a simplified interface.

servicenow.com

To create a module that directs users to a Record Producer UI:

Link Type Selection: Choose "URL (from Arguments:)" as the Link Type. This option allows you to specify a direct URL, enabling the module to open the desired Record Producer interface.

URL Configuration: In the "Arguments" field, input the URL that points directly to the Record Producer. This URL typically follows the format:

/record_producer.do?sys_id=

Replace with the actual sys_id of the Record Producer you intend to open.

By configuring the module this way, users accessing it will be presented with the Record Producer's user-friendly interface, facilitating the creation of new records without navigating through the standard form UI.

To link a ServiceNow application to a Git repository, you need to provide the user name, URL, and password of the Git account that hosts the repository12. The URL is the address of the Git repository that you want to link to the application. The user name and password are the credentials that you use to access the Git account. Alternatively, you can use a personal access token instead of a password for increased security3.

References = 1: Link an application to source control - ServiceNow Docs 2: Publish an application to the application repository - ServiceNow 3: Linking an application to Git using a personal access token instead of a password - ServiceNow

The purpose of application scoping is NOT to provide a way of tracking the user who developed an application. Application scoping does not store or display information about the user who created or modified an application or its artifacts. The purpose of application scoping is to provide a relationship between application artifacts, provide a namespace to prevent cross-application name collisions, and provide controls for how scripts from another scope can alter tables in a scoped application. References: [Product Documentation | ServiceNow], [Advantages of Scoped Applications in ServiceNow]

In ServiceNow, the admin role includes all other roles implicitly. So if a user has admin, g_user.hasRole('any_role') returns true.

From ServiceNow Docs – g_user API:

“The hasRole() method returns true if the user has the specified role or is an admin.”

The data type of a field determines the format, validation, and display of the field value on a form. When selecting a data type for a field, you should consider the purpose and function of the field. The statements A, C, and D are correct for selecting a data type for a field. For example:

Use the Choice data type to limit options in a field: The Choice data type allows you to create a field that has a predefined set of options for the user to select from. The options can be displayed as a drop-down list, radio buttons, or checkboxes. For example, you can use the Choice data type for a field that indicates the priority of a task.

Use the Phone Number data type to automate phone number data validation: The Phone Number data type allows you to create a field that accepts and validates phone numbers. The field will automatically format the phone number according to the user’s locale and country code. For example, you can use the Phone Number data type for a field that stores the contact number of a user.

Use the string data type for a free-form text field: The string data type allows you to create a field that accepts any text input from the user. The field can have a maximum length of 255 characters. For example, you can use the string data type for a field that captures the short description of an incident.

The statement B is not correct for selecting a data type for a field. There is no Data data type in ServiceNow. To enter the date and time of day, you should use the Date/Time data type. The Date/Time data type allows you to create a field that accepts and displays a date and time value. The field will use a calendar widget and a time picker to help the user enter the value. For example, you can use the Date/Time data type for a field that records the due date of a task.

Flow Designer variables can store record data and complex data using the following data types:

Integer: A whole number that can be used in mathematical operations.

Array: A collection of items that can be accessed by their index or iterated over using a For each action.

String: Any kind of text, such as email addresses or the text contents of a file.

Define and Use Data Types in a Flow (Flow Designer)

Variable data types - Power Automate | Microsoft Learn

Product Documentation | ServiceNow

In ServiceNow, extending a table means creating a new table (child class) that inherits properties from an existing table (parent class). This inheritance includes fields, business logic, and other configurations, allowing for efficient reuse and customization.

Key Points:

Field Inheritance: The child table inherits all fields from the parent table. For example, if you extend the Task table, your new table will include fields like "short_description" and "priority."

Business Logic Inheritance: The child table also inherits business rules, client scripts, and other logic defined on the parent table, ensuring consistent behavior across related tables.

Access Controls: Access controls are not ignored; instead, the child table inherits the parent table's access controls. However, you can define additional access controls specific to the child table as needed.

Customization: While the child table inherits many properties, you can add new fields, scripts, and behaviors to tailor it to specific requirements without affecting the parent table.

https://docs.servicenow.com/bundle/rome-application-development/page/build/applications/concept/c_ApplicationScope.html

The correct statement regarding Application Scope is that applications downloaded from 3rd party ServiceNow application developers cannot have naming conflicts. Application Scope is a feature that identifies and isolates applications and their related artifacts from other applications. Each scoped application has a unique namespace identifier that consists of a prefix and a scope name. This prevents cross-application name collisions and ensures that only authorized scripts can access or modify data in a scoped application. References: [Product Documentation | ServiceNow], [How To Create a Scoped App in ServiceNow - YouTube]

Understanding Scoped Applications:Scoped applications in ServiceNow are designed to isolate and protect application-specific code and data. Server-side scripts within scoped applications can use the gs (GlideSystem) object for logging and debugging purposes. However, not all gs methods are appropriate or valid for scoped applications.

Valid Logging Methods in Scoped Applications:

gs.info():This method logs informational messages to the system log. It is commonly used for general-purpose logging when developers need to track execution flow or display debug data. Example:

gs.info('This is an informational log message.');

gs.error():This method logs error messages to the system log. It is used to indicate problems or issues encountered during script execution. Example:

gs.error('An error occurred during script execution.');

Incorrect Options Explained:

gs.debug() (Option B): This method is not valid in scoped applications. It is a legacy logging method available in the global scope but restricted in scoped applications.

gs.iog() (Option C): This is a typographical error and not a valid gs method in ServiceNow.

gs.logError() (Option E): This is not a recognized ServiceNow API method. To log errors, gs.error() is used instead.

Best Practices for Logging:

Logging should be meaningful and avoid unnecessary entries to keep logs clean and manageable.

Avoid excessive use of logging in production environments, as it can clutter the system logs and potentially degrade performance.

ServiceNow Developer Documentation on GlideSystem (gs)?.

SN Pro Tips on debugging and logging practices in scoped applications?.

The Create Branch operation is available from both Studio and the Git Repository. This operation allows you to create a new branch from an existing branch in your Git repository. You can use branches to work on different features or versions of your application without affecting the main branch. Reference: [Create a branch]

https://docs.servicenow.com/bundle/tokyo-platform-security/page/administer/contextual-security/concept/access-control-rules.html

The ServiceNow REST API is a web service that allows you to interact with the ServiceNow platform using HTTP requests and responses. The ServiceNow REST API supports the following methods:

POST: This method allows you to create a new record or execute an action on the ServiceNow platform. For example, you can use the POST method to create an incident or run a script.

GET: This method allows you to retrieve information from the ServiceNow platform. For example, you can use the GET method to get the details of a user or a table.

DELETE: This method allows you to delete a record or a resource from the ServiceNow platform. For example, you can use the DELETE method to delete an attachment or a workflow context.

PUT: This method allows you to update a record or a resource on the ServiceNow platform. For example, you can use the PUT method to update the state of a task or the value of a system property.

PATCH: This method allows you to update a record or a resource on the ServiceNow platform by sending only the changes. For example, you can use the PATCH method to update the short description of an incident or the order of a module.

The method COPY is not part of the ServiceNow REST API. There is no COPY method in the HTTP protocol. To copy a record or a resource on the ServiceNow platform, you need to use the POST method with the clone action.

Application developers configure ServiceNow using industry standard JavaScript to extend and add functionality. JavaScript is a scripting language that enables developers to create dynamic and interactive web pages, as well as manipulate data and logic on the server-side. ServiceNow provides various APIs and frameworks for developers to use JavaScript to customize and enhance the functionality of their applications, such as client scripts, UI policies, business rules, script includes, UI actions, and more. References: [ServiceNow Docs - JavaScript in ServiceNow], [ServiceNow Docs - Scripting in ServiceNow]

In ServiceNow, the Application Picker is a tool that allows developers to select the active application scope. When an application is selected from the Application Picker, it sets the Application Scope to that application. This means that any configurations, scripts, or customizations made will be associated with the selected application's scope. Therefore, the correct answer is D.

The other options are incorrect:

A. Selecting Global in the Application Picker sets the Application Scope to Incident: Selecting "Global" sets the scope to the global application, not specifically to Incident.

B. Global is a reserved application which does not appear in the Application Picker: The Global application does appear in the Application Picker and can be selected.

C. Selecting an application from the Application Picker does not set the Application Scope: Selecting an application does set the Application Scope.

For more detailed information, refer to the official ServiceNow documentation on Application Scope.

In ServiceNow, when importing data from external sources, the platform utilizes Import Sets to stage the data before transforming it into target tables. The mechanism that defines how data from the Import Set fields map to the fields in an existing ServiceNow table is called a Transform Map.

Transform Map: A Transform Map is a set of field mappings that determine the relationships between fields in an Import Set and fields in an existing ServiceNow table. It allows administrators to define how data should be transformed and inserted into the target table.

servicenow.com

Business Service Management Map: This is not related to data import processes. It pertains to visual representations of business services and their dependencies.

Schema Map Relationship Builder: The Schema Map provides a graphical representation of tables and their relationships within the database schema but does not handle data import mappings.

Data Sources: Data Sources define the origin of the data being imported (e.g., files, JDBC connections) but do not determine the field mappings between Import Sets and target tables.

The source control operation used to store local changes on an instance for later application is called a stash. A stash is a temporary storage area for uncommitted changes that are not ready to be pushed to a remote repository. Developers can use stashes to save their work in progress without committing it to the local repository or discarding it. Stashes can be applied later to restore the changes to the working directory, or dropped if they are no longer needed. References: [ServiceNow Docs - Stash local changes], [ServiceNow Docs - Source control]

Inbound email matching uses Watermarks and Subject lines (with record numbers like INC0010001) to associate emails with existing records.

From Email Handling Docs:

“ServiceNow uses Watermark IDs and subject lines containing record numbers to find the corresponding task or record when processing inbound email.”

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

"Add instructional text and other design elements to your forms by using form annotations in Form Builder." https://docs.servicenow.com/bundle/sandiego-application-development/page/administer/form-builder/task/create-form-annotations.html

https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/concept/c_ApplicationPicker.html

https://docs.servicenow.com/bundle/tokyo-platform-administration/page/administer/platform-events/reference/r_ScriptActions.html

In ServiceNow, when configuring a REST Message, the Endpoint specifies the URI (Uniform Resource Identifier) where the REST request is sent. This URI points to the resource on the external system that the REST message will interact with, whether it's to retrieve, update, create, or delete data.

Key Points:

Endpoint Definition: The Endpoint is a complete URL that includes the protocol (e.g., HTTP or HTTPS), the domain or IP address of the external server, and the specific path to the resource. For example: https://api.example.com/v1/resources.

Dynamic Endpoints: ServiceNow allows the use of variables within the Endpoint URL, enabling dynamic substitution at runtime. This is useful when the exact resource path or parameters need to be determined during execution.

Configuration in ServiceNow:

Navigate to "System Web Services" > "Outbound" > "REST Message."

Create a new REST Message or select an existing one.

In the REST Message record, define the Endpoint URL in the "Endpoint" field.

Example Scenario:

If you are integrating ServiceNow with an external ticketing system to retrieve incident data, the Endpoint might be something like https://api.ticketingsystem.com/incidents/{incident_id}, where {incident_id} is a placeholder that gets replaced with the actual incident ID at runtime.

https://docs.servicenow.com/bundle/tokyo-application-development/page/script/server-scripting/concept/c_ServerScripting.html

The Application Repository is a central location for storing, managing, and distributing custom applications developed on the Now Platform.

From Developer Site > App Repo:

“The ServiceNow Application Repository stores custom applications and enables developers to distribute applications across multiple instances in their organization.”