Comprehensive and Detailed Step-by-Step Explanation:

UI Action Types:

List banner button: A button that appears in the list view banner, allowing users to perform actions on multiple records or interact with the list itself.

Form button: A button that appears on a form, enabling users to execute server-side or client-side scripts.

Record navigation button: A button used to navigate between records or perform specific actions related to a record.

Why Other Options Are Incorrect:

Option B (Workflow action): This is not a valid UI Action type; workflows are managed separately.

Option D (List choice) and Option E (Form choice): These are not valid UI Action types; they might confuse users with list or form field options instead.

References:

ServiceNow Developer Documentation on UI Actions​.

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

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

 Tables that extend a table inherit the parent’s fields. Extending a table means creating a child table that shares the same columns and business logic as the parent table. For example, the Incident table extends the Task table, which means that all fields defined on the Task table are also available on the Incident table. Extending a table allows for reusing existing fields and behaviors without duplicating them on multiple tables. Reference: Table extension and classes

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.

References:

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

"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

Application Files are ServiceNow artifacts comprising an application. An application is a group of files and data that work together to provide a service or functionality. An application file is a specific type of file that belongs to an application, such as a table, a script, a form, a business rule, a UI action, etc. Application files define the structure, logic, and interface of the application. An XML export of an application’s table records, XML exports of an application’s Update Set, and CSV files containing data imported into an application are not examples of application files, as they are data formats that can be used to transfer or store information related to an application, but not the application itself. Reference: Application Files

A spoke is a scoped application that contains flow actions that can be used in Flow Designer. Spokes allow developers to create reusable actions that can be shared across applications and instances.

References:

Spokes - Product Documentation: San Diego - ServiceNow

Create a spoke - Product Documentation: San Diego - ServiceNow

Flow Designer Spokes - ServiceNow Developers

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

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

The ServiceNow App Repository is a central repository for all scoped applications that are published by all ServiceNow customers. It enables ServiceNow customers to upload and distribute applications between their instances. It also provides entitlements and version control for the applications.

References:

ServiceNow application repository

Application Development Platform – ServiceNow

App Repo - ServiceNow Developer Blog

A workflow is a tool that allows you to automate processes on the ServiceNow platform. A workflow consists of activities and transitions that define the logic and flow of the process. A workflow context is an instance of a workflow that is generated from a workflow version, executes activities, and follows transitions. A workflow context is associated with a specific record on a table and tracks the state and progress of the workflow. You can view and manage the workflow contexts from the Workflow Contexts module or the Workflow Contexts related list on a record.

The other options are not valid definitions of a workflow context. A checked out workflow is a workflow that is being edited by a user and has not been published yet. The table and conditions for a workflow are the criteria that determine when a workflow should run on a record. The business reason or process for a workflow is the purpose and function of the workflow.

References:

[Workflow overview]

[Workflow context]

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

"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

Comprehensive and Detailed Step-by-Step Explanation:

Caller Access Fields:

Accessible from: Defines where the scriptable component (e.g., Script Include) can be accessed, such as "All application scopes" or "This application scope only".

None: Disables access, making the component unavailable for external use.

Caller Restriction: Controls which callers or scripts can access the component.

Why Other Options Are Incorrect:

Option A (Allow Configuration): This is not a valid caller access option.

Option B (Caller Permission) and Option F (Caller Tracking): These are not valid or recognized options in ServiceNow.

References:

ServiceNow Developer Documentation on Caller Access Fields​.

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.

References:

Inbound Action scripts

[Record Producer scripts]

Comprehensive and Detailed Step-by-Step Explanation:

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.

References:

ServiceNow Developer Documentation on GlideSystem (gs)​.

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

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

"There are two possible ways to respond to events:

- Email Notification

- Script Action" - see this quote in link below:

https://developer.servicenow.com/dev.do#!/learn/learning-plans/tokyo/new_to_servicenow/app_store_learnv2_automatingapps_tokyo_responding_to_events

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]

Catalog Client Scripts and Catalog UI Policies are the client-side scripts that apply to Record Producers. Catalog Client Scripts allow you to add or modify functionality on a catalog item or record producer form. Catalog UI Policies dynamically change information on a catalog item or record producer form. UI Scripts, UI Actions, Client Scripts, and UI Policies do not apply to Record Producers. Reference: Catalog client scripts, Catalog UI policies

gs.print() and gs.log() are older and not available in scoped applications, whereas gs.debug(), gs.info(), gs.warn(), gs.error() work in both scoped applications and global are therefore are more versatile going forward in future versions.

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

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. References: Application Access, Business Rules

https://docs.servicenow.com/bundle/tokyo-application-development/page/app-store/dev_portal/API_reference/glideSystemScoped/concept/c_GlideSystemScopedAPI.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

The statement that is true for this script fragment is that the method returns true if the currently logged in user has the x_my_app_user role or the admin role. The g_user.hasRole() method is a client-side method that checks whether the current user has a specified role or set of roles. If no role is specified, it returns true if the user has any role. If one or more roles are specified, it returns true if the user has any one of the specified roles. However, this method always returns true if the user has the admin role, regardless of the role parameter. Therefore, in this case, the method returns true if the user has either the x_my_app_user role or the admin role. Reference: User Object Cheat Sheet, Checking user permissions

From the list below, the following is a reason an application might not be a good fit with ServiceNow:

Requires “as-is” use of low-level programming libraries. This is the correct answer because ServiceNow is a high-level platform that abstracts away the low-level details of the underlying infrastructure and technology stack. ServiceNow provides a rich set of APIs, tools, and features that allow users to develop applications without coding or with minimal coding. However, ServiceNow does not support the direct

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

The application name is not required to link a ServiceNow application to a Git repository. You only need to provide the URL, user name, and password of the Git repository, as well as the branch name and the authentication type. The application name is automatically generated based on the scope name of your application. Reference: [Link an application to a Git repository]

To receive email notifications, a user must have an active account and a valid email address in the user record. If either of these conditions is not met, the user will not be able to receive any email notifications from the system.

References:

Create an email notification

Example scripting for email notifications

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

The baseline behavior of a table in a privately-scoped application is that all application scopes can read from the table. A privately-scoped application is an application that restricts write access to its tables and resources to scripts within the same scope. However, read access is allowed by default for all scopes, unless the administrator explicitly denies it using an Access Control rule. This allows for data sharing between different applications while maintaining data integrity and security. References: [Product Documentation | ServiceNow], [Advantages of Scoped Applications in ServiceNow]

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

A UI Action is a button, link, or choice that can be clicked by a user to perform an action, such as submitting a form or running a script. The following are UI Action types:

List choice. This is a UI Action that appears as a choice list on a list of records. It can be used to perform an action on multiple records at once, such as deleting or updating them.

Form button. This is a UI Action that appears as a button on a form. It can be used to perform an action on the current record, such as saving or approving it.

List banner button. This is a UI Action that appears as a button on the banner of a list of records. It can be used to perform an action on the entire list, such as exporting or printing it.

The following is not a UI Action type:

Form choice. This is not a UI Action type, but a field type. A form choice is a field that displays a choice list on a form. It can be used to select a value from a predefined set of options, such as priority or state. References: UI Actions, Field Types

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

An Access Control list (ACL) defines what data users can access and how they can access it in ServiceNow tables1. The ACL evaluates the user roles and the conditions defined in the ACL rules to determine the user’s access level2. In this case, the ACL rules for the table are as follows:

table.None read Access Control for users with the admin and itil roles: This means that users with the admin or itil roles cannot read any field in the table unless there is a more specific rule that grants them access3.

table. * read Access Control for users with the admin role: This means that users with the admin role can read all fields in the table.

table. field3 read Access Control for users with the itil role: This means that users with the itil role can read only the field3 in the table.

Therefore, a user with the itil role can read only the field3 in the table, and not the other fields.

References = 1: Access Control Lists - ServiceNow Docs 2: How ACL Rules Are Evaluated - ServiceNow Docs 3: Access Control List Rules - ServiceNow Docs : Wildcard in ACL Rules - ServiceNow Docs : Field-Level ACL Rules - ServiceNow Docs

To see what scripts, reports, and other application artifacts will be in a published application, the best option is to examine the Application Files Related List in the application to be published. This will show all the application files that belong to the application, grouped by file type and scope. You can also filter, sort, or search the list to find specific files.

The following options are not the best ways to see what application artifacts will be in a published application:

Enter the name of the Application in the Global search field. This will perform a global text search on the instance and return any records that match the application name, which may include irrelevant or incomplete results.

Open the list of Update Sets for the instance. This will show all the update sets that have been created or imported on the instance, but not necessarily the ones that belong to the application to be published. Update sets are used to move customizations between instances, not to publish applications to the ServiceNow Store or Share.

Open the artifact records individually to verify the value in the Application field. This will require opening each record that may be part of the application and checking the Application field, which is tedious and error-prone. References: Publish an Application, Application Files

Access Controls are rules that define who can access what data and how they can access it. When configuring an Access Control, you can specify the table, operation, and role for the rule. You can also add a condition or a script to further refine the rule. If you do not add a condition or a script, the rule will apply to all records and fields on the table.

The statements A, B, and C are true for Access Controls that have no condition or script. For example:

table.* will grant access to every field in a record. This means that the user can view and edit all the fields on the record, regardless of their role or any other criteria.

table.None will grant access to every record on the table. This means that the user can view and edit all the records on the table, regardless of their role or any other criteria.

table.field will grant access to a specific field in a record. This means that the user can view and edit only that field on the record, regardless of their role or any other criteria.

The statement D is not true for Access Controls that have no condition or script. table.id will not grant access to a specific record on the table. This is because the id is not a field name, but a unique identifier for the record. To grant access to a specific record on the table, you need to add a condition or a script that matches the id of the record.

References:

[Access Control rules]

[Create an Access Control rule]