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?

[Community Alums]

Messy and has a lot of risk for inconsistency. One of the benefits from using a system like ServiceNow is so you can define consistent processes. Think about it from an 80/20 perspective and try to create a flow that could handle the majority of your cases to keep them consistent. From there you can consider the requests that cannot be handled through that flow, possibly even working in a way in the workflow to have something a little more open ended.

I've had discussions with customers about these types of processes and what it looks like when someone wants to request something that is not already defined in the catalog (try to get users to select defined items first that already have the appropriate vendor agreements behind them, including any security checks, negotiations, etc. with those vendors). Otherwise you create a lot of extra work to handle all requests the same way you might instead just handle "one offs."