SNOW-CSA Service Catalog and Workflows — 10 Questions

Question 1

A company wants to ensure that when a user submits a catalog item for a new laptop, the request is automatically approved if the cost is under $1,000 and the user's department has sufficient budget. What is the best way to implement this requirement?

Accepted Answer

Create an Approval rule with conditions on cost and department budget.. Option D is correct because Approval rules in ServiceNow are specifically designed to automate approval decisions based on conditions like cost and department budget. By creating an Approval rule on the catalog item, you can evaluate the requested cost against a threshold and check the department's budget balance via a condition script or reference to the budget table, enabling automatic approval without manual intervention.

Answer

Configure a notification to inform the user of the approval status.

Answer

Set up a Business Rule to approve all requests under $1,000.

Answer

Use a Flow to send an approval request to the manager every time.

Question 2

A Service Catalog item has a variable that asks for the user's manager's email. The variable type is 'Email'. When the user submits the item, the manager should receive a notification. How should the variable be configured to ensure the email is valid?

Accepted Answer

Use the 'Email' variable type; it includes validation.. The 'Email' variable type in Service Catalog automatically validates that the entered value conforms to a standard email format (e.g., user@domain.com). This built-in validation ensures the manager's email is syntactically correct before the notification is triggered, without requiring additional scripting or regex. Option D is correct because it leverages this native validation, which is the simplest and most reliable method.

Answer

Set the variable as 'Read only' and rely on data from sys_user table.

Answer

Add a regular expression in the variable's 'Regex' field.

Answer

Use a 'String' variable and add a client script to check format.

Question 3

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?

Accepted Answer

The variable's 'Display' property is set to 'Static' or 'Read only'.. Option D is correct because 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 4

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.. Option C is correct because 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 5

A user complains that when they submit a catalog item, they receive an error: 'The variable is mandatory but has no value.' However, the variable is not marked as mandatory in the item's variable definition. What could be the cause?

Accepted Answer

A Catalog Client Script of type 'onSubmit' sets the variable mandatory.. Option A is correct because a Catalog Client Script of type 'onSubmit' can dynamically set a variable as mandatory using the `g_form.setMandatory('variable_name', true)` method. This overrides the variable's definition in the catalog item, causing the 'mandatory but has no value' error even when the variable is not marked mandatory in the item's variable definition.

Answer

A Business Rule on the request table sets the variable mandatory.

Answer

A UI Policy on the record producer makes the variable mandatory.

Answer

The variable is mandatory in the parent catalog category.

Question 6

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 can have default values that reference other variables using syntax like '${variable_name}'. This allows dynamic default values based on user input or system data, which is a key feature for creating adaptive catalog forms.

Answer

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

Answer

Once created, the order of variables cannot be changed.

Question 7

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 the 'Workflow' field on the catalog item record directly associates a workflow with that item. When a user submits the catalog item, the platform automatically triggers the associated workflow on the generated sc_request record. This is the standard declarative method for linking a catalog item to a workflow without custom scripting.

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 8

Refer to the exhibit. A catalog item has a variable 'department' (choice list with values 'IT', 'HR', 'Finance') and a variable 'cost_center' (choice list initially empty). The client script is supposed to add an option to 'cost_center' when 'department' is set to 'IT'. However, when a user selects 'IT', no new option appears. What is the most likely reason?

Accepted Answer

The variable 'cost_center' is not a 'Choice' variable type.. Option A is correct because the `g_form.addOption()` method only works on variables of type 'Choice' (or similar select-type variables like 'Select Box'). If 'cost_center' is not a Choice variable, the client script cannot dynamically add options to it, and the method call silently fails or has no effect. In ServiceNow, only choice-based variable types support runtime option manipulation via client-side APIs.

Answer

The script is a server-side script and cannot use 'g_form'.

Answer

The script needs to call 'g_form.clearOptions()' before adding options.

Answer

The method should be 'g_form.addOption()' with different syntax.

Question 9

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.. Option B is correct because 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 10

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.. Option A is correct because 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.