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]

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.

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.

References:

• Flow Designer – No-Code Workflows - ServiceNow
• Flow Designer - ServiceNow
• Flow Designer Data Sheet - ServiceNow

There is no "copy" button on the application record (at least I couldn't see one). Also, see here: https://docs.servicenow.com/bundle/sandiego-application-development/page/build/applications/reference/r_ManagingApplications.html

The following is true for GlideUser (g_user) methods:

• Can be used in Client Scripts, UI Policies, and UI Actions. This is true because GlideUser (g_user) methods are part of the client-side scripting APIs that provide information about the current user and the user’s preferences. Client Scripts, UI Policies, and UI Actions are all types of client-side scripts that run in the web browser and manipulate the user interface.

The following are not true for GlideUser (g_user) methods:

• Can be used in Client Scripts and UI Policies only. This is false because GlideUser (g_user) methods can also be used in UI Actions, which are another type of client-side scripts that can be triggered by a user’s click on a button, link, or choice.
• Can be used in Business Rules only. This is false because GlideUser (g_user) methods cannot be used in Business Rules, which are server-side scripts that run on the ServiceNow platform and manipulate the database. Business Rules use a different API to access the current user information, which is GlideSystem (gs).
• Can be used in Business Rules, and Scripts Includes. This is false because GlideUser (g_user) methods cannot be used in Business Rules or Script Includes, which are both server-side scripts. Script Includes are reusable units of code that can be called from any server-side script. Script Includes also use GlideSystem (gs) to access the current user information. References: Client-Side Scripting APIs, GlideUser, Business Rules, Script Includes

"Guided Application Creator is enabled via the Guided Application Creator (com.glide.sn-guided-app-creator) plugin, which is active by default in the Now Platform." Located under "Activation Information" section at this URL:

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

Web services are software systems that use standardized protocols and formats, such as XML and HTTP, to exchange data and messages between different applications or systems over the Internet or other networks12. Web services enable interoperability and integration among diverse software components, regardless of their programming languages, platforms, or architectures34.

References = 1: What are Web Services? - GeeksforGeeks 2: Web service - Wikipedia 3: What are Web Services? - Online Tutorials Library 4: What is a Web Service? | Webopedia

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 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]

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

When evaluating Access Controls, ServiceNow searches and evaluates:

• From the most specific match to the most generic match. This is the correct answer because ServiceNow follows a top-down approach when evaluating Access Control (ACL) rules, which are used to restrict the access to the data and functionality of the ServiceNow platform based on the user’s roles and conditions. ServiceNow starts with the most specific match, which is the field-level ACL rule, then moves to the table-level ACL rule, and finally to the global or * ACL rule. ServiceNow grants access if any of the ACL rules evaluates to true, and denies access if all of the ACL rules evaluate to false.

The following are not correct descriptions of how ServiceNow searches and evaluates Access Controls:

• Only for matches on the current table. This is not correct because ServiceNow does not only look for matches on the current table, but also on the parent tables and the global or * table. For example, if there is no ACL rule for the incident table, ServiceNow will look for an ACL rule for the task table, which is the parent table of the incident table, and then for the global or * table, which is the parent table of all tables.
• Only for matches on the current field. This is not correct because ServiceNow does not only look for matches on the current field, but also on the table that contains the field and the global or * table. For example, if there is no ACL rule for the short_description field on the incident table, ServiceNow will look for an ACL rule for the incident table, and then for the global or * table.
• From the most generic match to the most specific match. This is not correct because ServiceNow does not follow a bottom-up approach when evaluating Access Controls, but a top-down approach, as explained above. References: Access Control Rules, ACL Evaluation Order

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

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()]

Creating applications in ServiceNow can help businesses replace outdated, inadequate, custom business applications and processes, extend service delivery and management to all enterprise departments, and extend the value of ServiceNow by leveraging its platform capabilities and integrations1234.

References = 1: What are Application Services? - ServiceNow 2: What is Application Development? - ServiceNow 3: Custom Applications in ServiceNow - The Cloud People 4: Build Custom Apps in ServiceNow – eBook – ServiceNow

The following roles grant access to source control repository operations such as importing applications from source control, or linking an application to source control:

• source_control. This is a role that allows users to perform basic source control operations, such as importing an application from a source control repository, updating an application from a source control repository, or committing changes to a source control repository.
• admin. This is a role that grants full access to all the features and functions of the ServiceNow platform, including source control operations. Users with this role can also perform advanced source control operations, such as creating or deleting source control repositories, configuring source control properties, or resolving conflicts.

The following roles do not grant access to source control repository operations:

• source_control_admin. This is not a valid role in ServiceNow. There is no separate role for source control administration, as this function is included in the admin role.
• git_admin. This is not a valid role in ServiceNow. Git is a specific type of source control system that ServiceNow supports, but there is no role dedicated to Git administration. References: Source Control, Source Control Roles

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

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/useful-scripts/reference/r_DisplayFieldMessages.html

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

The Field Watcher is a debugging tool that allows you to monitor the values of fields on a form as they change due to scripts or other actions. It can be used to debug Business Rules, Client Scripts, and Access Controls, but not Script Includes. Script Includes are server-side scripts that define reusable functions and classes. They are not associated with any specific field or form, and therefore cannot be watched by the Field Watcher.

References:

• Field Watcher
• Script Includes

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

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

The method call that returns true only if the currently logged in user has the catalog_admin role and in no other case is g_user.hasRoleExactly(‘catalog_admin’). This method checks if the user has exactly one role, and returns true if it matches the argument. The other methods return true if the user has one or more roles, or if the user has any role from a list of arguments. References: [ServiceNow Docs - GlideUser API], [ServiceNow Community - Difference between hasRole() and hasRoleExactly()]

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.

References:

• [Access Control scripts]
• [GlideSystem methods]
• [GlideRecord methods]

The step that does not belong when creating a Utils Script Include is identifying the table. A Script Include is a server-side script that can contain one or more classes or functions that can be reused by other scripts. It does not depend on a specific table, but can access any table through GlideRecord or other APIs. The other steps are part of creating a Script Include class and its prototype object. References: [ServiceNow Docs - Script Includes], [ServiceNow Docs - GlideRecord API]

Created UI policy on incident form, action set's cmdb_ci field as mandatory and script as not. result, field was not mandatory.

A UI Policy’s Actions execute before the UI Policy’s Scripts. Actions are predefined operations that can be applied to fields or sections, such as making them mandatory, read-only, visible, or setting a default value. Scripts are custom JavaScript code that can be used to perform more complex logic or validations. Actions are executed first, and then Scripts are executed if the UI Policy conditions are met. References: [ServiceNow Docs - UI policy actions], [ServiceNow Docs - UI policy scripts]

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

https://docs.servicenow.com/bundle/tokyo-servicenow-platform/page/administer/notification/task/t_CreateANotification.html

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

The Weight field in an Email Notification determines which notification is sent when multiple notifications are triggered for the same record and recipients. Only the notification with the highest weight is sent. A weight value of zero means the notification is always sent when the notification’s When to send criteria is met. A weight value of -1 means that no email should be sent3. References: Email Notification Weight

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

The statement that is not true for Modules is that every Module must be associated with a table. A Module is the functionality within an Application Menu that opens a content page in the content frame or a separate tab or window. A Module can be associated with a table, a list, a form, a report, a script, or any other type of page. For example, the Open Module under the Incident Application Menu opens a list of incident records from the Incident table, while the Overview Module under the Performance Analytics Application Menu opens a dashboard page with various charts and widgets. The other statements are true for Modules. Access to Modules is controlled with roles, as each Module can have one or more roles specified in its definition that determine who can see and access it. Modules open content pages, as they are links to different types of pages that provide information and functionality to users. Every Module must be part of an Application Menu, as they are the second-level navigation options for Applications. Reference: Modules

Self-invoking. Learn JavaScript!

This type of JavaScript function is known as self-invoking or immediately-invoked function expression (IIFE). It is a function that is defined and executed at the same time, without being assigned to a variable or being called by another function. It is often used to create a local scope for variables and avoid polluting the global namespace. References: [W3Schools - JavaScript Function Definitions], [MDN Web Docs - Immediately-invoked function expressions]

In the SOAP Message feature set, we indicate variables using the following syntax: S{variable_name}. This allows us to pass a variable with the specified name from the SOAP message record to the web service function.

References:

• Tutorial: Handling a SOAP Response in ServiceNow | John Andersen
• ServiceNow SOAP - Cheat Sheet Cheat Sheet by bibingokuldas - Download …

The welcome screen appears every time a new application is created through the Guided Application Creator. The welcome screen provides an overview of the steps involved in creating an application, such as defining the app name, scope, and tables, configuring the app user interface, and publishing the app. The other options are not true about the Guided Application Creator. The global scope option is turned off by default, as it is recommended to create applications in their own scope for better security and performance. A scope application user role is not automatically created, as the user can choose to create one or use an existing role for the app access control. Default access controls are not automatically created, as the user can define the read, write, create, and delete permissions for each table in the app. Reference: Guided App Creator

https://docs.servicenow.com/bundle/rome-platform-administration/page/administer/reference-pages/task/schedule-report.html Generate and distribute scheduled reports via email.

A report is a graphical representation of data from one or more tables in ServiceNow. The following are true for reports in ServiceNow:

• Can be a graphical representation of data. This is true because reports can use various chart types, such as pie, bar, line, or gauge, to visualize data in a meaningful way.
• Can be run on demand by authorized users. This is true because reports can be accessed from the Reports menu or the Report Navigator and run by users who have the appropriate roles and permissions to view the data.
• Can be scheduled to be run and distributed by email. This is true because reports can be configured to run at a specific time and frequency and send the results to one or more email recipients.

The following are not true for reports in ServiceNow:

• Any user can see any report shared with them. This is false because users can only see reports that are shared with them if they also have access to the data source of the report. For example, a user who does not have the itil role cannot see a report based on the incident table, even if the report is shared with them.
• All users can generate reports on any table. This is false because users can only generate reports on tables that they have access to and that are enabled for reporting. For example, a user who does not have the admin role cannot generate reports on the sys_user table, which is the table for user records. References: Reports, Report Security

The ServiceNow Store is a marketplace for free and paid certified ServiceNow applications and integrations. The ServiceNow Store provides customers with access to Now Certified enterprise workflow apps from partners that complement and extend ServiceNow products and solutions. Customers can browse, try, buy, and deploy apps and integrations that suit their needs and enhance their ServiceNow experience. The ServiceNow Store is not the source for ServiceNow Community created developer content, as that is available on the Developer Portal or the Share site. The ServiceNow Store is not a downloadable content ServiceNow script archive, as that is available on the Script Library or the Script Repository. The ServiceNow Store is not an alternate name for the ServiceNow Developer Share site, as that is a separate site where developers can share applications, code snippets, UI pages, etc. Reference: ServiceNow Store

 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