Linking RITM to Standard Change

[brianlan25]

Back in 2022 when we went like with change we created a file on the sc_req_item table called u_change_request. We then created a UI action to create a standard change with the following code.

// will redirect user to create a standard change and will fill the u_change_request custom field.
action.setRedirectURL(new StdChangeUtils().getURLForTask(current, 'u_change_request'));
 
action.setReturnURL(current);

Recently we got Yokohama Patch 13 Hotfix 4 and this suddenly no longer works. Any idea on what my we causing this? Note that I noticed that action.setReturnURL(current) is not in the code for the same UI action on Incident so I have tried to comment that out that code as well. Note that this is still working on incident the only difference is that incident is using the out of the box rfc field.

Edit: This note about it working on incident was wrong. The ATF template for incident that I copied was not validating that change number was associated to the incident. Since the incident test did not fail I thought it was working for incident.

[brianlan25 · Accepted solution]

Figured this out. This code seems to work if you turn on 2 step in the system properties for standard change. We had that turned off. This seems to be the only way to get it to work in my PDI as well. As soon as I turned off two step it does not work.