On Universal task table type field is showing no choices in dropdown

Praju_123
Tera Contributor

Tuesday

 

I installed all the required plugins to enable the Universal Request feature. However, when I try to create a Universal Task inside the Universal Request, the Type field on the Universal Task form shows no available choices.

I checked the out-of-the-box (OOB) configuration and found that this field should display choices based on certain fields (as shown in Image 1). To fix this, I created those choices as shown in Image 2, but they still don’t appear in the form.

I’m also attaching a screenshot of the Universal Task form for reference.

Praju_123_0-1768306739026.png

Praju_123_1-1768306831595.png

Praju_123_2-1768306892114.png

 

 

0 Helpfuls
  • 83 Views
2 REPLIES 2

Gaurav Rathaur
Mega Guru

Tuesday

@Praju_123 ,

 

The Type field on Universal Task is dynamically populated in ServiceNow. It depends on the Universal Request Type and OOB configuration. Choices are not sourced from sys_choice, so manually adding them will not work.

Resolution

  • Ensure the Universal Request Type is populated on the parent Universal Request

  • Create Universal Tasks only via OOB flows/actions, not manually

  • Do not add manual sys_choice records for this field

  • Verify no custom UI Policies, Client Scripts, or Dictionary overrides exist on the Type field.

Mark this answer helpful if it solves your problem.

0 Helpfuls

SIVASANKARIS
Giga Guru

Tuesday

Hi @Praju_123 ,

Refer this ==>https://www.servicenow.com/docs/bundle/yokohama-employee-service-management/page/product/universal-t...

It outlines the fundamental setup steps required to make Universal Task functional for a specific service (like IT or HR).

The reason your manual choices aren't appearing is that the Universal Task framework doesn't just look at the sys_choice table; it filters choices based on the Service Task Configuration. If you haven't performed the configuration steps mentioned in your doc, the "Type" field will remain empty because the system doesn't know which types are valid for your specific "Service."

 

In the Document

The sections "Configure Universal Task for your service" and "Configure the catalog items for your service" are the keys to fixing the empty Type field.

 

How to Fix the "Missing Type Choices" Issue

Following the logic in your documentation, you need to link your Service (e.g., HR or IT) to the Universal Task types.

1. Define the Service Task Configuration

  1. Navigate to Universal Task > Administration > Service Task Configuration.

  2. If one doesn't exist for your table (e.g., sn_hr_core_case or incident), create a New one.

  3. Select the Parent Table (this is the "Service" table where your Universal Request lives).

2. Register the Task Types for that Service

Inside that Service Task Configuration record you just created:

  1. Look for the Universal Task Types related list at the bottom.

  2. Click New or Edit.

  3. This is where you define the "Types" (like Upload Document, Collect Input, etc.) that should be available for that service.

  4. Important: The choices you see on the form are driven by this list, not just the standard sys_choice table.

3. Match your Manual Choices (Image 2)

If you created custom choices in sys_choice (your Image 2), they must have a Dependent Value that matches the Name or Sys ID of the Service Task Configuration. If the dependent value is missing or incorrect, the "Type" field will filter them out because it doesn't think they belong to the current service context.

 

Summary of what to do next:

  • Step 1: Check if a Service Task Configuration exists for your parent table.

  • Step 2: Ensure the "Types" you want are added to the Universal Task Types related list within that configuration.

  • Step 3: Ensure the Universal Request record itself has the "Service Configuration" field populated so the task knows which rules to follow.

 

If this is useful.. please mark it as helpful and accept my solution....

0 Helpfuls