Why does SCTASK gets created instead of TASK?

[John Vo1]

Does anyone know why when I submit a REQ and Task gets created it shows sctask instead of task?

[The SN Nerd · Accepted solution]

The Catalog Task table extends task and is used OOB in conjunction with the Service Catalog.

It has fields pertinent to the Service Catalog that do not exist on the Task table.

You can see the number prefix definition in "System Definition > Numbers" where 'Table' is "sc_task"

[darius_koohmare]

Hi John,

This is based on how ServiceNow has structured its tables.

In our world, the 'Task' table is a parent table from which many Task types (incidents, problems, changes, catalog tasks, etc.) have been extended from. By doing so, the extended tables inherent the fields that exist at the top 'Task' level.

Now we create a Catalog Task in the context of a Requested Item, because a requested item is generally to fulfill a catalog item request. This Catalog Task table is defined so that its prefix is SCTASK (or service catalog task).

We wouldn't use TASK, because TASK is for the parent table.

[John Vo1]

So in my Prod instance this is what I see.

But this is in my Dev instance.

[The SN Nerd]

They will be the same table with a different numbers configuration.

I think they changed the numbering prefix from a particular version and i bet your instances are probably running different versions.

Compare the number definitions in each system.