How to populate the Change request created below the CR related list

[sandhya2249]

In a catalog, standard change request is getting created in RITM and it is getting updated in the work notes like (CR has been created from RITM). But it is not tagged under the Change Request Related List in RITM. Kindly suggest how to populate the Change request created below the CR related list.

[danmjunqueira]

This is a common issue when a Change Request is created from a catalog item (RITM) via a script or flow, but it doesn’t appear in the Change Request related list under the RITM. That related list depends on a reference field being properly set.

Root Cause
The Change Request (Change record) is not linked back to the RITM (Requested Item) via the correct reference field.

By default, the related list is based on the Request Item field on the change_request table:

Field: request_item (on change_request)

Type: Reference → sc_req_item

If this field is not populated, the related list in the RITM will remain empty.

To populate the Change Request under the Change Request related list in the RITM, follow these steps:

1. When creating the Change Request record from the catalog item, set the request_item field on the change_request record to point to the RITM.

Example using script:

var change = new GlideRecord('change_request');
change.initialize();
change.short_description = 'Created from RITM';
change.request_item = current.sys_id; // assuming current is the RITM
change.insert();

Once the request_item field is set correctly, the related list will appear automatically in the RITM form under the Change Request section.

If you are using Flow Designer or a workflow, ensure that the Change Request action or script step includes a way to set the request_item field to the RITM's sys_id.

Make sure the related list is configured on the RITM form layout. Go to the RITM form and check that the Change Request related list is added via Form Layout or Form Design.