SNOW-CSA Service Catalog and Workflows — Timed 20 Questions

Question 1

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?

20 minute time limit — choose an answer to begin.

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 2

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.. 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 3

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 4

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'.. 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 5

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 6

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

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

Accepted Answer

Variables can have default values that reference other variables.. 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 8

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.. 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 9

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.. 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 10

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 11

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 12

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.. Adding the CI's assigned support group to the watch list of the CI record ensures that the group receives email notifications when the request is submitted. This leverages the platform's notification engine, which sends emails to users and groups in the watch list of the record. Option C is also correct because a Reference variable pointing to the cmdb_ci table allows the user to select a specific CI from the CMDB, which is required for the catalog item to know which CI is affected.

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 13

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 14

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 15

Drag and drop the steps to create a new Business Rule in ServiceNow into the correct order.

Accepted Answer

Navigate to System Definition > Business Rules, then Click 'New', then Configure rule (name, table, condition, order), then Write script, set Active, and Submit. The correct order starts by navigating to System Definition > Business Rules to access the Business Rules module. Then click 'New' to create a new rule. Next, configure the rule by setting the name, table, condition, and order to define when it runs. After configuration, write the script that contains the logic to execute. Finally, set the rule as active and click Submit to save and enable it. This sequence ensures that the rule is properly defined before writing the script and that all settings are complete before activating.

Answer

Click 'New', then Navigate to System Definition > Business Rules, then Configure rule, then Write script and Submit

Answer

Navigate to System Definition > Business Rules, then Configure rule, then Click 'New', then Write script and Submit

Answer

Navigate to System Definition > Business Rules, then Click 'New', then Write script, then Configure rule and Submit

Question 16

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 17

A catalog item has a variable 'Department' and another 'Cost Center'. The Cost Center should only be visible when Department is 'IT'. Which configuration is most efficient?

Accepted Answer

Catalog UI policy with a condition on Department. A Catalog UI Policy can conditionally show or hide variables on a catalog item based on the value of another variable (e.g., Department = 'IT') without requiring a record to exist or a submission to occur. It runs client-side in real-time as the user fills out the form, making it the most efficient and immediate approach for controlling visibility based on a field value.

Answer

Workflow stage that sets visibility after submission

Answer

Catalog client script on the Cost Center variable's onChange event

Answer

Variable set with a condition on Department

Question 18

A user reports that a catalog item's 'Requested for' field is not being set correctly after submission. The catalog item uses a workflow that includes a 'Set Requested For' activity. What is the most likely cause?

Accepted Answer

The 'Set Requested For' activity is configured with a static user value. The 'Set Requested For' activity in a ServiceNow workflow explicitly overrides the 'Requested for' field on the catalog item. If it is configured with a static user value, it will always set that user regardless of who submitted the request, causing the reported issue. This is the most direct cause because the activity's configuration takes precedence over the default behavior of populating the field with the requester.

Answer

The workflow context variable for requested for is missing

Answer

The workflow is not published

Answer

The catalog item variable mapping is incorrectly configured

Question 19

A catalog item uses a workflow with a 'Run Script' activity that contains a script to update a custom table. The script works correctly when executed manually in the Scripts Background, but fails when invoked by the workflow. What is the most likely reason?

Accepted Answer

The workflow runs with a different security context, causing permission issues. The most likely reason is that the workflow runs under the security context of the workflow engine (typically the 'workflow' user or the system user), not the current user's context. When the script is executed manually in Scripts Background, it runs with the full privileges of the admin user, which may include write access to the custom table. In contrast, the workflow's Run Script activity may lack the necessary ACL permissions (e.g., write or create) on the custom table, causing the GlideRecord update to fail silently or throw an error.

Answer

The workflow script references a variable that is undefined in that context

Answer

The script uses incorrect GlideRecord API methods

Answer

The workflow is in draft mode

Question 20

A catalog item has a variable 'Country' and another 'State'. The State variable should be mandatory only when Country is 'USA'. What is the most efficient way to achieve this?

Accepted Answer

Catalog UI policy with condition on Country. The most efficient way is to use a Catalog UI Policy (Option A). A Catalog UI Policy can set the mandatory attribute of a variable based on a condition on another variable, such as making 'State' mandatory when 'Country' equals 'USA'. This is declarative and requires no scripting. Option B (Workflow with a 'Set Mandatory' activity) acts after submission and cannot make a field mandatory before submission. Option C (Variable set with mandatory condition) is for grouping variables and does not enforce mandatory conditions. Option D (Catalog client script on Country's onChange event) is possible but requires more coding and is less supportable than a UI Policy.

Answer

Workflow with a 'Set Mandatory' activity

Answer

Variable set with mandatory condition

Answer

Catalog client script on Country's onChange event