CAD: ServiceNow Certified Application DeveloperDemo

ServiceNow REST API Explorer can generate sample code for REST requests sent to a ServiceNow instance.

A business process should document the business problem, the required data inputs and outputs, the users and stakeholders involved, and the process steps. These describe the process’s purpose, information flow, participants, and workflow; project schedules, license availability, and database capacity are not core business-process documentation elements.

The Create a User ATF test step creates a test user with the required roles and group memberships. ServiceNow recommends this approach instead of impersonating an existing user, and rolls back the created test data after the test completes.

ServiceNow reports visualize current instance data, can be run to view current data by users with the appropriate reporting access, and can be scheduled for distribution by email. Access is role- and permission-dependent, and reporting is not available to every user on every table.

An application scope establishes an isolation boundary around an application's files, data, and other resources. Other applications cannot access or modify those resources unless explicitly permitted through cross-scope access controls.

Script Includes hold reusable server-side functions or classes that run when another script calls them. Because they are loaded on request, they can improve efficiency; shared logic is maintained in one location. A protected Script Include also protects intellectual property by preventing customers who install the application from seeing the script contents.

A spoke is a scoped application that contains reusable Flow Designer actions and integration-related content.

A completed ServiceNow update set cannot capture additional changes. Further work must be captured in a new update set.

A private application scope gives application artifacts a unique namespace, which prevents naming and code collisions. Scoped applications are packaged as a cohesive application, enabling them to be installed and uninstalled as an application.

A user must pass the table ACL and the applicable field ACL. The itil role passes the table.None read ACL, but does not pass the more specific table.field3 read ACL because that ACL requires the admin role. Thus, the user can read field1 and field2, but not field3.

The ServiceNow Application Repository stores custom ServiceNow applications so they can be published, versioned, and installed on other instances.

A Transform Map defines the data relationships between an Import Set table and a target ServiceNow table through its field maps. It specifies how source fields are mapped and transformed into destination fields.

Inbound email action scripts provide the current object for the record associated with the inbound email and the email object for the current inbound email. previous and producer are not available inbound-action script objects.

Flow Designer supports reusable subflows, delegated-developer access, and MetricBase-triggered flows. Testing a flow runs its actions against instance data; it does not include a rollback mechanism to undo the changes made by the test.

A record producer is a type of Service Catalog item. Its form supports associated Catalog Client Scripts and Catalog UI Policies, which control client-side behavior for its variables and form presentation.

Design-time Application Access controls whether other application scopes can create configuration records that extend an application's data tables. Restricting Accessible from to This application scope only denies that design-time access to all other private scopes. The Can create option instead controls runtime creation of data records, not configuration records.

Sections group and organize related fields within a form.

ServiceNow application-sharing methods include publishing to the application repository for instances in the same company, publishing to the ServiceNow Store for other ServiceNow customers, and publishing to an Update Set for instances that can access the Update Set file.

Per the ServiceNow CAD material, the Flow Designer variable data types supported for storing record and complex data among these options are Integer (B), Array.Reference (C), and String (E). Array.Reference stores a collection of record references (complex/record data), while Integer and String are the supported primitive value types listed. "Label" (A) is not a flow variable data type, and "Choice" (D) is not one of the three in the keyed answer. This matches both the official flow-variable documentation and multiple CAD answer keys.

The client-side GlideRecord API is not supported in scoped applications. Database access from scoped client scripts should instead use a client-callable Script Include through GlideAjax (or an appropriate REST API).

A Before Business Rule can use the current record and, on update or delete operations, the previous record. Both are GlideRecord-based record objects, and server-side Business Rule scripts can also create and use GlideRecord instances to access other records.

Outbound ServiceNow REST messages use ${variable_name} for variable substitution; the REST message replaces the token with the parameter value when the method executes.

The Run As property sets the identity under which a flow executes—either the system user or the user who initiated the session. Flow testing runs a saved flow with supplied test data; Run As is not a test-as-user feature. Flow Designer does support Service Catalog-triggered flows and stages.

The Classic UX format supports both list and form interfaces, making it the appropriate format when an experience requires both types of record interaction.