I need to create Change Task after RITM

[AbdurRahmanSnow]

Good morning. 
I have a requirement, that on the Catalog form, we have a Change Request field. So, before submitting the form, the user should have created a Change Request first, then only he can fill out the form.
Once form is submitted, RITM gets created and under it, we need to create Change Task, instead of SCTASK.

I have achieved this using scripting in workflow. But the problem is, Change Task is getting created under the Change Request, which we created earlier, but not under RITM. But it should also get attached on the RITM>Change Task.
How to achieve this? 

The script is below which works but Change Task is not getting attached on the RITM, (although it getting attached under the Change Request).

WorkFlow Run Script 1:

workflow.info('Run Script Checking 1');

var cNumber = current.variables.change_request_number_1;

var gr = new GlideRecord('change_request');

gr.addQuery('sys_id', cNumber);

gr.query();

if (gr.next()) {

    current.u_application = gr.getValue('u_application');

    workflow.scratchpad.appName = gr.getValue('u_application');

}

______________________________________________________________

WorkFlow Run Script 2 for Change Task:

workflow.info('Run Script Checking 3' + current.variables.change_request_number_1);

workflow.info('workflow.scratchpad.appName' + workflow.scratchpad.appName);

var gr = new GlideRecord('change_task');

gr.addQuery('change_request', current.variables.change_request_number_1);

gr.query();

if(gr.next()){

    gr.initialize();

    gr.setValue('change_request', current.variables.change_request_number_1);

    gr.setValue('u_application', workflow.scratchpad.appName);

    gr.setValue('assignment_group', '58c5a8940f3c62407b3a3e7ce1050ed2');

    gr.setValue('short_description', 'Change Task has been created for Assignment group AP Digital Products Support');

    gr.insert();

}

[Ankur Bawiskar]

@AbdurRahmanSnow 

change_task should get associated with CHG only and not RITM

Why would you want to associate it with RITM?

RITM has CHG and CHG has change Task

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

[Ankur Bawiskar]

@AbdurRahmanSnow 

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.

[Dr Atul G- LNG]

Hi @AbdurRahmanSnow 

By process your requirement is not valid, the change task gets created in the Ctask table and catalogue task get created in the SCtask table, so what is your business use case to link task in task.

[blaze1]

Here’s the situation from a ServiceNow architectural perspective:

ServiceNow is designed to maintain distinct processes for Change Management and Service Catalog. Each of these has its own workflow and record structure, and they aren't typically intended to be tightly coupled in the way you're requesting.

Why it doesn't work as expected:
RITMs (Requested Items) are part of the Service Catalog process, which is focused on fulfilling user requests for services or products. These records are designed to track requests for services, not changes to the system itself.
Change Requests and Change Tasks are part of Change Management, which is focused on managing and controlling changes to IT services and infrastructure. They are designed to have their own lifecycle, approvals, and relationships that are separate from catalog requests.
In your case, the Change Task is being created under the Change Request, which is correct according to the Change Management model. However, ServiceNow does not natively allow for attaching Change Tasks directly under RITMs, because these are separate process flows with their own objectives.

Options you can explain to leadership:
Keep workflows separate but linked: We can consider having the Change Request created as part of the catalog item’s workflow, but still keep them as separate records. You could link the Change Request to the RITM (for traceability), but the Change Task would still belong to the Change Request. This way, we respect ServiceNow’s out-of-box structure while still providing the necessary linkage for tracking.

Custom Scripting: While it’s possible to create custom scripts to force a Change Task under a RITM, this would break the separation of workflows and could lead to complications with the standard Change Management and Service Catalog processes. The custom code would need to handle these relationships explicitly, which could be prone to errors and maintenance challenges over time.

Reconsider process flow: We could evaluate whether a different process design would be more in line with ServiceNow’s intended use. For example, the Change Request could be triggered based on certain conditions in the Service Catalog form, but the Change Task would remain under the Change Request, which is the correct place for it.

Key Point for Leadership:
While the requirement to tie Change Tasks to RITMs is technically feasible, it is not how ServiceNow is designed to operate, and implementing this could introduce unnecessary complexity and potential long-term issues. I recommend keeping these workflows distinct to ensure that we align with best practices, maintain system stability, and minimize future maintenance.

[AbdurRahmanSnow]

Thank you for your valuable reply, Blaze. Really appreciate.