SNOW-CSA Service Catalog and Workflows — 40 Questions

Question 1

A catalog item uses a 'Catalog Client Script' to hide a variable when another variable is set to 'No'. However, the script is not working. The script is of type 'onChange' and the variable to hide is a 'Single Line Text'. What is the most likely cause?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

The variable's 'Display' property is set to 'Static' or 'Read only'.. When a variable's 'Display' property is set to 'Static' or 'Read only', the client-side script cannot override that setting via `g_form.setDisplay()`. The catalog client script runs on the client, but the variable's display behavior is enforced by the platform's UI policy layer, which takes precedence over client script calls. This is a common misconfiguration where the variable's display property is locked, preventing the onChange script from hiding it.

Answer

The variable type 'Single Line Text' does not support hiding.

Answer

The script is missing a 'g_form.setDisplay()' call.

Answer

The script should be of type 'onSubmit' instead of 'onChange'.

Question 2

An administrator needs to create a workflow that sends an email to the approver when a request is approved, and sends a different email when the request is rejected. What is the appropriate workflow component to use for this branching logic?

Accepted Answer

Use an 'Approval' activity with two 'Outcome' branches.. The 'Approval' activity in ServiceNow workflows inherently supports branching via 'Outcome' branches. When an approval is processed (approved or rejected), the workflow engine evaluates the outcome and follows the corresponding branch, allowing you to attach different email notifications to each path without additional logic activities.

Answer

Use a 'Timer' activity to delay and then check state.

Answer

Use a 'Begin Approval' activity and then a 'Decision' activity.

Answer

Use a 'Condition' activity to check the approval state.

Question 3

Which THREE of the following are true about Service Catalog variables? (Choose three.)

Accepted Answer

Variables can have default values that reference other variables.. Option C is correct because Service Catalog variables support default values that can dynamically reference other variables (for example, using a variable's name in a script or default value expression), enabling dependent or pre-populated input. Option D is correct because each variable's Type (such as Single Line Text, Reference, Select Box, or Checkbox) dictates the UI control rendered on the catalog form and how the user interacts with it. Option E is correct because variables can be reordered by editing the numeric 'Order' field in the variable list (or via the question's variable editor), which controls their sequence on the form. Option A is incorrect because catalog variable definitions and values are stored in tables like 'item_option_new' and 'sc_item_option'/'question_answer', not 'sys_variable'. Option B is incorrect because the order of variables is not fixed; it can be changed at any time using the Order field.

Answer

All catalog variables are stored in the 'sys_variable' table.

Answer

Once created, the order of variables cannot be changed.

Question 4

Which TWO of the following are valid ways to trigger a workflow from a catalog item? (Choose two.)

Accepted Answer

Set the 'Workflow' field on the catalog item to the desired workflow.. Option C is correct because a catalog item record has a 'Workflow' field (a reference to a Workflow record) that, when populated, causes that workflow to be launched automatically when the item is ordered and the request is submitted. Option E is correct because Flow Designer flows can be configured with a 'Record Created' trigger on the Request [sc_request] table, which is a supported way to initiate processing (including workflow-style orchestration) when a catalog item generates a request. Option A is incorrect because there is no 'Workflow' tab on the catalog item form; the workflow is set via the Workflow field, not a separate tab. Option B is incorrect because a Business Rule on sc_request that manually starts a workflow is a custom workaround, not a standard/valid catalog-item trigger mechanism. Option D is incorrect because 'Execute Workflow' is not a standard workflow activity used to point back to a catalog item to trigger it; workflows are triggered by the catalog item's Workflow field or via Flow Designer triggers.

Answer

On the catalog item form, go to the 'Workflow' tab and select a workflow.

Answer

Write a Business Rule on the 'sc_request' table that starts a workflow.

Answer

In the workflow editor, add a 'Execute Workflow' activity pointing to the catalog item.

Question 5

Refer to the exhibit. A workflow for a catalog item has three stages. The 'Run Script' activity sets the assigned_to to the current user (the requester). The approval activity approves by the manager. The 'Create Task' activity creates a catalog task. When the workflow runs, the task is created but is assigned to the requester instead of the fulfillment group. What is the likely cause?

Accepted Answer

The 'Run Script' activity sets the assigned_to on the request, but the task creation activity does not copy that value; the task should have its own assignment.. The 'Run Script' activity sets the `assigned_to` field on the request record itself, but the 'Create Task' activity creates a separate catalog task record. The task creation activity does not automatically inherit the `assigned_to` value from the request; it uses its own assignment configuration, which defaults to the requester if no fulfillment group or specific assignment is defined. This causes the task to be assigned to the requester instead of the intended fulfillment group.

Answer

The task creation activity is configured to assign to the requester by default.

Answer

The workflow should have a 'Set Values' activity after the approval to assign the task.

Answer

The approval activity reassigned the request to the manager.

Question 6

A large enterprise uses ServiceNow for IT service management. They have a catalog item 'New Employee Setup' that is used by HR to request IT resources for new hires. The catalog item includes variables for employee name, start date, department, and manager. The workflow associated with this item creates a catalog task for the desktop team to prepare a laptop, and another catalog task for the network team to create accounts. Recently, the desktop team has been receiving tasks with incomplete information; the employee name variable is sometimes empty even though it is marked as mandatory. The administrator checked the variable definition and confirmed 'Mandatory' is set to 'true'. The variable is a 'Single Line Text' with no default value. The issue happens intermittently. What course of action should the administrator take to resolve this issue?

Accepted Answer

Add a workflow script activity that checks if the variable is empty and rejects the request if so.. The issue is that the mandatory field validation is being bypassed intermittently, likely due to the catalog item being submitted via a web service, REST API, or an integration where client-side mandatory checks are not enforced. Adding a workflow script activity that checks the variable value server-side ensures that even if the client-side validation fails, the request is rejected before proceeding, providing a reliable server-side guard.

Answer

Reorder the workflow activities so that the validation occurs earlier.

Answer

Change the variable type to 'Email' to enforce stronger validation.

Answer

Set the variable to 'Read only' and populate it from a reference field.

Question 7

A ServiceNow administrator needs to create a service catalog item that requires the user to select a configuration item (CI) that will be affected by the requested service. The catalog item should also send an email notification to the CI's assigned support group when the request is submitted. Which TWO actions must the administrator take?

Accepted Answer

Create a business rule or flow that adds the CI’s assigned support group to the watch list of the CI record upon catalog item submission.. Option C is correct because a Reference variable pointing to the Configuration Item [cmdb_ci] table is the standard way to let a user select a CI on a catalog item, storing the selected CI's sys_id in the request's variable data. Option B is correct because ServiceNow does not automatically notify a CI's assigned support group on catalog submission, so the administrator must implement logic (a business rule or Flow Designer flow) that reads the selected CI's support group and adds it to the watch list so the notification reaches that group. Option A is not correct because 'CI Selector' is not a valid ServiceNow variable type; the CI is selected via a Reference variable to cmdb_ci. Option D is not correct because a notification on the catalog item alone would not target the CI's assigned support group, which is the stated requirement. Option E is not correct because the requirement is to notify the CI's support group, not to overwrite the CI record's Assigned group field.

Answer

Use a variable of type 'CI Selector' to allow selection of a CI.

Answer

Set up an email notification on the catalog item itself to send when the request is submitted.

Answer

Configure the catalog item to automatically populate the 'Assigned group' field on the CI record.

Question 8

Refer to the exhibit. A ServiceNow administrator created a catalog item that allows users to select a CI via a reference variable named 'ci'. The business rule shown is supposed to update the CI's operational status to 'In Production' when the requested item is closed complete. However, the CI status is not being updated. What is the most likely cause?

Accepted Answer

The script does not properly retrieve the CI record because current.variables.ci returns the sys_id but may not be accessible directly in an after business rule without using the sc_item_option table.. In an 'after' business rule on the Requested Item (sc_req_item) table, the variable values from the catalog item are not directly accessible via current.variables.ci. Instead, they are stored in the sc_item_option table and must be retrieved using a GlideRecord query on sc_item_option joined to the requested item's sys_id. The script attempts to use current.variables.ci, which does not resolve to the CI's sys_id in this context, causing the update to fail.

Answer

The condition 'current.state.changesTo(3)' is incorrect; it should check if the state is already 3.

Answer

The reference variable 'ci' is not storing the sys_id of the CI; it stores the display value.

Answer

The business rule runs 'Before' instead of 'After', so the state hasn't changed yet.

Question 9

A large enterprise uses ServiceNow for IT service management. The Service Catalog includes a 'New Employee Setup' bundle that contains multiple catalog items such as 'Create AD Account', 'Assign Laptop', and 'Provision Email'. Each catalog item has its own workflow. Recently, the 'Assign Laptop' catalog item has been failing intermittently. The workflow that runs for this item includes an approval step and several tasks. When the workflow fails, the requested item shows a state of 'Work in Progress' and the workflow context shows an error: 'The workflow could not find the activity named: Approve Laptop'. The workflow has an approval activity named 'Approve Laptop' and it is active. The approval activity is set to 'Run as' the workflow user. The workflow is associated with the catalog item correctly. The failure occurs only when the request is submitted by users who are not in the 'IT' role. What is the most likely cause of the failure?

Accepted Answer

The workflow user does not have sufficient rights to execute the approval activity when the requester lacks the 'IT' role.. The error 'The workflow could not find the activity named: Approve Laptop' indicates that the workflow engine cannot locate the approval activity at runtime. Since the approval activity is set to 'Run as' the workflow user, and the failure occurs only when the requester lacks the 'IT' role, the most likely cause is that the workflow user does not have sufficient rights (e.g., missing the 'approver' role or ACL permissions) to execute the approval activity when the requester's role triggers a security context restriction. This is a common permission issue in ServiceNow workflows where the execution context of the activity depends on the requester's roles.

Answer

The 'Approve Laptop' approval activity is deactivated.

Answer

The catalog item is not correctly linked to the workflow.

Answer

The approval activity requires a specific approval group that is not defined.

Question 10

Match each ServiceNow user role to its typical permission.

Accepted Answer

admin: Full administrative access to all modules. Roles in ServiceNow define user permissions. Admin has full access, ITIL handles ITIL processes, User has basic self-service, Approver can approve requests. Common confusion is mixing admin with approver or user with ITIL.

Answer

admin: Permission to approve or reject requests

Answer

user: Access to ITIL processes such as incident, problem, and change management

Question 11

A catalog item is configured to use an order guide. When a user submits the order guide, only the first catalog item in the guide appears. What is the most likely cause?

Accepted Answer

The order guide's 'Delivery method' is set to 'One at a time'. When an order guide's 'Delivery method' is set to 'One at a time', the system processes only the first catalog item and stops, rather than adding all items to the cart. This setting is designed for scenarios where each item must be ordered individually, so submitting the guide results in only the first item appearing.

Answer

The workflow attached to the order guide is incomplete

Answer

The catalog items have mandatory variables that are not filled

Answer

The order guide is in a restricted category

Question 12

A catalog client script is used to populate a variable's value from an external table. The script works in the development instance but fails in production. Which troubleshooting step should be taken first?

Accepted Answer

Verify that the script's 'Run as' and 'Global' flags are set correctly in production. Catalog client scripts run in the browser context, and their behavior depends on the 'Run as' (user impersonation) and 'Global' flags. In production, these flags may differ from development, causing the script to fail silently if it lacks permissions to query the external table or if it is scoped incorrectly. This is the first step to check because it directly affects script execution context and data access.

Answer

Ensure the external table exists in the production instance

Answer

Review the system logs for script errors

Answer

Check if the workflow attached to the catalog item is active

Question 13

A catalog item uses a 'Variable set' that includes several variables. After updating the variable set, the changes do not appear on the catalog item form. What is the most likely cause?

Accepted Answer

The variable set cache has not been cleared. ServiceNow caches variable set definitions to improve performance. When a variable set is updated, the cache must be cleared (via 'Cache Flush' or by deactivating/reactivating the variable set) before the changes are reflected on the catalog item form. Without clearing the cache, the system continues to serve the stale, cached version of the variable set.

Answer

The variable set is not published

Answer

The catalog item's category has been changed

Answer

The catalog item is shared with a restricted role

Question 14

Which THREE are valid ways to bring data into a catalog item variable?

Accepted Answer

Lookup select box that references a table. Option A is correct because a Lookup Select Box variable type can reference a table and dynamically pull records (e.g., sys_user or cmn_location) as selectable values for the catalog item variable. Option C is correct because record producer variable mapping lets a producer's variables be mapped to fields on the target record, effectively bringing data into the catalog item variable context from the producer. Option E is correct because a variable's Default value can be set via a script (using the 'Default value' script field or a dynamic default), which populates the variable with data at form load. Option B is not a valid mechanism for bringing data into a catalog item variable; workflow context variables are used within workflow/flow execution, not as a variable data source. Option D is incorrect because a Catalog Client Script on submit runs client-side logic at submission time and does not itself serve as a data source for populating a variable.

Answer

Workflow context variable

Answer

Catalog client script on submit

Question 15

Which TWO conditions are necessary for a catalog item to trigger a workflow automatically upon submission?

Accepted Answer

The workflow must be in 'Published' state. Option A is correct because a workflow must be in the 'Published' state to be selectable and executable; unpublished (draft) workflows cannot be triggered by a catalog item submission. Option E is correct because the catalog item's 'Workflow' field must reference a specific workflow — if that field is empty, no workflow will run automatically when the item is submitted. Together, these two conditions ensure that a valid, active workflow is actually attached to the item. Option B is incorrect because workflow execution is not governed by the catalog item's category; categories are for organization and display, not for enabling workflow logic. Option C is incorrect because workflows are not 'subscribed' to catalog items; the association is made by populating the catalog item's Workflow field, not through a subscription mechanism. Option D is incorrect because while a 'Begin' activity is a normal part of workflow design, its presence alone does not cause automatic triggering — the workflow must be published and linked to the item.

Answer

The catalog item must be in a category that allows workflow execution

Answer

The workflow must be subscribed to the catalog item

Answer

The workflow must contain a 'Begin' activity

Question 16

A catalog item has a variable of type 'Single Line Text' with a default value. Users report that when they submit the request, the default value is not being used. A catalog client script that runs on submit is setting the variable to empty string. What is the most likely cause?

Accepted Answer

Client script runs before default value is applied. Catalog client scripts that run on the 'onSubmit' event execute before the default value is applied to the variable during the submission process. Since the script sets the variable to an empty string, it overrides the default value before it takes effect.

Answer

Variable is mandatory

Answer

Client script runs after submit cancels default

Answer

Default value is only for display, not submission

Question 17

An administrator notices that a catalog client script is not firing when a variable changes. The script is set to 'onChange' and the variable reference is correct. The script uses g_form.setValue to update another variable. However, the other variable does not get updated. What could be the issue?

Accepted Answer

The variable being updated has a catalog client script that clears it. When a catalog client script uses g_form.setValue to update another variable, that action triggers the onChange event for the target variable. If the target variable has its own onChange catalog client script that clears its value, that script will execute after the setValue, effectively overriding the update. This creates a conflict where the first script sets a value, but the second script immediately clears it, resulting in the variable appearing unchanged.

Answer

The other variable's value is protected by a UI policy

Answer

The script is running on the server side

Answer

The script is using g_form.setValue incorrectly for that variable type

Question 18

A catalog item variable has a reference qualifier that limits the choices to active users only. However, users can still select inactive users. What is the most likely cause?

Accepted Answer

The reference qualifier is written incorrectly. Reference qualifiers in ServiceNow are always server-side. They are evaluated when the catalog item is loaded and when the record is saved. If inactive users are still selectable, the most likely cause is that the reference qualifier script is incorrectly written or missing. Therefore, option D is correct. Option A is incorrect because the 'any' setting does not bypass reference qualifiers. Option B is incorrect because admin role does not ignore reference qualifiers for variables. Option C is incorrect because reference qualifiers do not run on the client side; they are server-side only.

Answer

The variable is set to allow 'any' value

Answer

The user has admin role and ignores qualifier

Answer

The reference qualifier uses JavaScript that runs on the client but not server

Question 19

A catalog item has a variable with a mandatory condition: if the variable 'category' is 'software', then 'software name' is mandatory. This is best implemented using:

Accepted Answer

UI Policy. A UI Policy is the correct choice because it allows you to define a mandatory condition on a catalog item variable without writing any code. In this case, you would create a UI Policy that runs when the 'category' variable is 'software', and within that policy set the 'software name' variable's mandatory attribute to true. This is the standard, no-code approach for enforcing variable-level mandatory conditions in Service Catalog.

Answer

Catalog Client Script

Answer

ACL

Answer

Variable Condition

Question 20

A record producer is configured to use table 'incident' and has a mapping that sets the short description from a variable. When the record producer is submitted, no incident is created. Which is the most likely cause?

Accepted Answer

The table does not have a mandatory field that is not mapped. The most likely cause is that the target table (incident) has a mandatory field that is not mapped in the record producer's mapping. When a record producer creates a record, it must satisfy all mandatory field requirements of the target table; if a mandatory field is missing or unmapped, the system will fail to create the record, often without an explicit error to the user.

Answer

The user does not have rights to create incidents

Answer

The variable mapping uses a wrong syntax

Answer

The record producer is not active