Should you create sc task by a record producer

[johansec]

If you dont have anything to do other than to create a catalog task, should you create the catalog task using a record producer instead of a catalog item. My vote is no but I have a teammate who is dead set on it. I think this should not be done like this because you may need to add approvals later and there are notifications and ui's that are created to show this. 

Please let me know if you have ever done this or if it is recommended to do this. 

[Ankur Bawiskar · Accepted solution]

@johansec 

Not recommended.

That's now how OOTB Catalog task is meant for

It's always meant to be linked with RITM and REQ submitted for it

That's correct here going forward if there are approvals etc then it's not to good to have it on Catalog tasks

Catalog tasks are the tasks which agents need to work to fulfill the request

Inform your friend to go through the ITIL process.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Ankur Bawiskar]

@johansec 

Thank you for marking my response as helpful.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Ankur Bawiskar]

@johansec 

Hope you are doing good.

Did my reply answer your question?

If my response helped please mark it correct and close the thread so that it benefits future readers.

[sunil maddheshi]

@johansec 

Catalog Item – Preferred for Structured Catalog Requests

Use Case: Anything that’s meant to go through the Service Catalog flow — meaning it might involve:

• Approvals

• Notifications

• Service Portal representation

• Request/Requested Item (REQ/RITM) tracking

• Task generation (Catalog Tasks)

• SLAs, workflows, fulfillment, etc.

You just want to create a record in another table (e.g., incident, change, custom table). It's like a form shortcut that doesn’t go through the catalog flow.

Record producers do not create REQ or RITM records, so:

• You miss out on built-in notifications and SLAs.

• You don’t get Service Portal visibility (My Requests, etc.).

• There’s no approval flow unless you build it manually.

• Not designed to handle complex fulfillment logic.

Please mark correct/helpful if this helps you!