Difference between the REQ, RITM, SCTASK, TASK? Need to know the Flow of these creations. Decribe briefly about the relationships between them? Which one is parent table and which one is the child table? Any kind of help will be appreciable

[SrinivasPkl]

Difference between the REQ, RITM, SCTASK, TASK?

Need to know the Flow of these creations. Decribe briefly about the relationships between them?

Which one is parent table and which one is the child table?

Any kind of help will be appreciable

[Mehernosh Amrol]

Have the development team can bring the contact/"Requested for" information into the SCTASK form? This should be a simple configuration to the form. 🙂

Have a good weekend.

[Lubo1]

Hi,

is there any common definition/understanding on what can be managed over Tasks?

In our case - we're using REQs and RITMs. However I tend to consider a misuse of SCTASK as we're receiving many Enhancement requests through SCTASKs while my understanding is that SCTASK should only cover some minor service request but not the Enhancement or new configuration.

Anyone has the same problem or understanding? How do you use it within your teams?

thank you.

[Mehernosh Amrol]

Hi,

I guess it depends on other modules and access in your environment.  My particular team will use requests to take an enhancement request, review it, discuss it with the Requestor, and then create a story.

the REQ/RITM/SCTASK, can vary based on your environment.  Requesting Hardware/Software, requesting a new Service Catalog, or updates.

I would suggest looking into the types of enhancement requests, the modules, and then discussing with your ServiceNow leadership team as to what is best for the different requests.

Hope that helps,

M.

[Lubo1]

Thanks,

from our perspective we use it for Application support here. However I figured out our setup is just basic - whatever is not break/fix, is marked as Enhancement. Some space for improvements I guess... 🙂

[Yogesh Verma1]

A task represents a business-meaningful activity that needs to be done. If you see from the developers point of view, task is the base table of REQ (sc_request), RITM (sc-req_item), SCTASK (sc_task) tables.

Wondering what that means? (see the point below)

• REQ, RITM and SCTASK tables are being inherited from the task table.
• Or you can say REQ, RITM, and SCTASK tables are the child tables whose parent table is the TASK table.
• TASK table is the base table for the above three tables.

Now, whenever you submit a catalog item or multiple catalog items (through a cart), given below are the things that will get created in the instance.

1. A single request will be created.
2. Under that request, there might be one or more than one requested items (RITM's) get created (If you have submitted the request by adding multiple catalog items in a cart, then in this case more than one RITM's will be created).
3. Now according to the configuration that you have done in the flow or workflow at the back-end, under a single requested item (RITM), one or more than one SCTASK will get created.

I hope this answers your question. Let me know if you need any further clarification.