Hello Sandrine,
Luckily ServiceNow has a method for doing this. For example, when you create a request from an Incident, the Incident is populated as the parent of the request within the sc_request table automatically. In order to extend this capability to additional tables, such as Change Requests, ServiceNow provides a module called "Request Parent Mapping". I've added the Change Request table to this mapping as shown below:
From there, you can add the UI action to create a request from a change by doing an insert and stay on the "Create Request" UI Action that is seen within the Incident Table, the resulting UI Action is below (make sure to edit the conditions so that the UI Action is appropriately shown within the change table). Once this is completed, you'll be able to create Requests from Change that automatically associate with the change through the parent field.
Table: change_request
Condition: Edit per requirements.
Script:
//Update saves Change before going to the catalog homepage
current.update();
var url;
var activeCatalogsCount = sn_sc.Catalog.getCatalogCount();
if (activeCatalogsCount === 1) {
url = "catalog_home.do?sysparm_view=catalog_default&sysparm_parent_table=" + current.sys_class_name + "&sysparm_parent_sys_id=" + current.sys_id;
}
else {
url = "catalogs_home.do?sysparm_view=catalogs_default&sysparm_parent_table=" + current.sys_class_name + "&sysparm_parent_sys_id=" + current.sys_id;
}
action.setRedirectURL(url);
I'm not sure that I understand you correctly. Change form contains by default two Related Lists "Incidents Fixed by Change" and "Incidents Caused by Change", which allows to link incidents to Change.
The first list sets Change Request [rfc] field of incident and the second one sets Caused by Change [caused_by] field of incident. If required you can display the fields on the Incident form.
Hello Sandrine,
Luckily ServiceNow has a method for doing this. For example, when you create a request from an Incident, the Incident is populated as the parent of the request within the sc_request table automatically. In order to extend this capability to additional tables, such as Change Requests, ServiceNow provides a module called "Request Parent Mapping". I've added the Change Request table to this mapping as shown below:
From there, you can add the UI action to create a request from a change by doing an insert and stay on the "Create Request" UI Action that is seen within the Incident Table, the resulting UI Action is below (make sure to edit the conditions so that the UI Action is appropriately shown within the change table). Once this is completed, you'll be able to create Requests from Change that automatically associate with the change through the parent field.
Table: change_request
Condition: Edit per requirements.
Script:
//Update saves Change before going to the catalog homepage
current.update();
var url;
var activeCatalogsCount = sn_sc.Catalog.getCatalogCount();
if (activeCatalogsCount === 1) {
url = "catalog_home.do?sysparm_view=catalog_default&sysparm_parent_table=" + current.sys_class_name + "&sysparm_parent_sys_id=" + current.sys_id;
}
else {
url = "catalogs_home.do?sysparm_view=catalogs_default&sysparm_parent_table=" + current.sys_class_name + "&sysparm_parent_sys_id=" + current.sys_id;
}
action.setRedirectURL(url);
