Is there a way to manually create tasks or changes from a service catalog request

[tcorniels]

Is there a way to manually create tasks or changes from a service catalog request?

Example:

User requests a new server to be built through the service catalog.   This request will be sent to the Server Team for approval.   If approved, the Network and Middleware teams may have tasks that need to be completed as part of this request.   These would need to be created manually (somehow).   Also, a change may need to be created to put the server into the production environment once it is built.   This would also need to be manually created.   Neither the tasks nor the change would be related in any way to the request otherwise.

Alternatively, would it be better to have the service catalog request create a change instead of a request so tasks can be created easier?

[Ravi Prasad1]

Yes you can create manual catalog tasks or change requests by using New button on the related list as shown below.

[Community Alums]

Why manually create these tasks? I would have the tasks created as part of the Requested Item workflow. You could use ifs as part of the Workflow if you don't want to create these tasks every time.

[tcorniels]

Part of what we are being asked to build is kind of a "catch-all" request form.   So anybody can request ANYTHING, which means way more possibilities than we could probably plan and program for.

My thinking is if we can have a basic workflow that queues the initial request to the user-specified group for approval, then allow the approval group to spawn their own tasks as necessary to complete the requested item.

[Uncle Rob]

Yes, you can manually create sc_tasks on a RITM ***BUT*** it will have absolutely no interaction with the RITM's workflow.

I'm with Ben.   Don't manually create SC_Tasks if you can get workflow to do it for you.   I've built in capabilities to have manual task additions, but it was only in cases where a component of the flow did not necessarily exist (like an extra testing or documentation task or something).   I then include scripts in the workflow that re-evaluate whether or not the workflow can close.

Its messy messy messy.