How to make 'Incidents fix by Change' mandatory in change request?

[Hermes14]

Hi,
how do i make the incident fix by change mandatory in the related list tab in change request?

[Dr Atul G- LNG · Accepted solution]

Hi @Hermes14 

You can use a BR to make it mandatory, but the question is—does an incident always get fixed through a change in practical scenarios? Rethink this approach, but yes, you can enforce it as mandatory if needed.

https://www.servicenow.com/community/itsm-forum/mandatory-related-list/m-p/813518

https://www.servicenow.com/community/itsm-forum/how-to-make-related-list-as-mandatory/m-p/827850

[Ankur Bawiskar]

@Hermes14 

can you please share screenshot of the form and the related list?

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

[Hermes14]

Hi,
here are the screenshots

[Ankur Bawiskar · Accepted solution]

@Hermes14 

you can use before update business rule and check and abort the update.

Condition: Category Changes to Service

Script:

(function executeRule(current, previous /*null when async*/ ) {

    // Add your code here
    var gr = new GlideRecord("incident");
    gr.addQuery("rfc", current.sys_id);
    gr.query();
    if (!gr.hasNext()) {
        gs.addErrorMessage('Please add data in related list');
        current.setAbortAction(true);
    }

})(current, previous);

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

[Hermes14]

just a follow up question, how can I make it not move to the next state?

[Ankur Bawiskar]

@Hermes14 

you can update the business rule condition with the correct state transition

State Changes To XYZ and State Changes From ABC