Hi Steve, I’m not sure how you could deal with that. You’ll probably need to contact ServiceNow support to investigate.

Thanks Mark for the quick reply. I thought that would be the case as well and wondered if there was any other quick way of doing this. Will give this a try :)

This can certainly be done, you would need to perform a query against the ‘question_answer’ table using a similar routine to the one found in the sample script above and perform inserts of any records found.

Here are the corrections that I had to make for this script to work as intended:

– When setting the change_request on the new task, a sys_id of the task should be used:
==> newTask.change_request = newChange.sys_id;

– In the code for copying task attachments the second sys_id should be of the new task:
if (typeof GlideSysAttachment != ‘undefined’)
GlideSysAttachment.copy(‘change_task’, taskID, ‘change_task’, newTask.sys_id);//Calgary and up
else
Packages.com.glide.ui.SysAttachment.copy(‘change_task’, taskID, ‘change_task’, newTask.sys_id);//pre Calgary

Thank you again!

There are ways to do that, but it’s actually fairly complicated. I’ve seen some discussions on the ServiceNow community about this, but haven’t really seen anything that covers all of the bases outside of what we do at Crossfuze in our turnkey change product.

We allow the user to do 2 things. The first is that they can change the ‘Type’ field as long as the change is in a draft state. This allows for some flexibility in selecting the change type before you get into the full workflow. The second thing we’ve done is create a custom interceptor concept that routes the user to an intermediate record producer form that allows us to ask for details about the change…type, etc. before actually creating the change. Since it’s a part of our proprietary code base, I can’t share the details, but I would be willing to do a demo of the solution for you if you’d like to take a look.

My question is, how can I incorporate this script but allow the user to select the Change Type so that the appropriate work flow is associated.

Thanks again.

I’m not sure what might be the issue. These scripts have been tested and verified before. Please try copying and pasting from here and testing in a ServiceNow demo instance.