Task vs CTask vs SCTask

[Ardalan]

Hi, can anyone clarify the key differences between a regular (TASK), a Change Request task (CTASK) and a Service Catalog SCTASK).  a comparison table will be great. Thanks 

[b__SravanS]

follwing

[jMarshal]

TASK is a base table, CTASK and SCTASK are extended from that....so all fields that are on TASK will be on CTASK and SCTASK.

CTASK is (as you identified) a Change Task, it has additional fields to link it to a CHG record and relate to the Change Management process. Conceptually, a CTASK record is always the child record of a CHG record (which is not itself a task record itself, even though I believe it still extends the TASK table), in a many to one relationship.

SCTASK is (as you identified) a Service Catalog Task, it has additional fields to link it to a RITM record and relate to Serviced Catalog/Request Fulfillment functions. An SCTASK record is always the child record of a RITM record (which itself is the child of a REQ record). The only way to initiate/create an SCTASK is from a Catalog item by way of the defined process engine for that item (which is usually a Flow). Again, the SCTASK records are in a many to one relationship with RITM records and I believe both RITM and REQ extend TASK as well.

In theory, you can create TASK records (on the base table) and assign them out in the platform (to anyone with a fulfiller license)...but in practice you should logically compartmentalize the TASKs which you are assigning, within the module that they belong to (in the case of CTASK and SCTASK, that would be the ITSM module)...if you want to have some other custom TASKs, you should scope an app and extend TASK to a custom table.

I hope this helps! Please give a thumbs-up or accept-as-solution if so...if not, feel free to ask a follow-up question. Thanks in advance!

[b__SravanS]

In terms of complexity, development and implementation, what are key differences and similarities b/w CTASK and STRY? 

From this, we want to understand why CTASKS cannot be estimated like we do for Stories

[Dr Atul G- LNG]

SCTASK and Story are indeed two distinct modules in ServiceNow, serving entirely different purposes:

1. SCTASK (Service Catalog Task):

   • It is used within the Service Catalog/Request Management process.
   • Tasks can be created and assigned to different teams to fulfill specific catalog items or requests.
   • It focuses on operational work related to service delivery and support.

2. Story:

   • Part of Agile 2.0, used to capture user requirements in an agile development process.
   • Stories allow you to estimate effort, define acceptance criteria, and track the time required for development.
   • It focuses on planning and executing development work within sprints.