RITM variables to a change request record

[booher04]

We have a need to map catalog item variables from an RITM to a change request record.  Currently on our RITMs we have a related list for our change request(related request) so that someone can create a new change from the RITM.  What we'd like to do is take a few of the variables from the Catalog Item that are on the RITM and when we go to create a new change request on the RITM, map some variables to fields on the change.  Is this possible?  I know that you can map the variables to the "description field" on the change.  

[Allen Andreas]

Hi,

Please see this thread which talks about where those variables are located in, within your instance and also provides a script pretty much set up mostly for you to use to get those: https://community.servicenow.com/community?id=community_question&sys_id=798a8be9db5cdbc01dcaf3231f96...

This sort of explains where they are and how to get them...to next question would be are you going to use this in a UI Action perhaps to allow users to use the Context Menu or click a Button to allow them to create a change request that way from your RITM.

So it'd be a different step than the user clicking "New" down in the change_request related list.

Please mark reply as Helpful/Correct, if applicable. Thanks!

[booher04]

Hi Allen.  Thanks for the response.  

To your question, yes I thought about using a UI Action with a button at the top with something like "Create Change".  I wasn't sure if that would be the best route as I only need it(for now) to show on RITMs for one particular catalog item(Database Request).  As of now, the users have been going to the related list, selecting "new" on the interceptor they select "normal", then they go to the change request and create it.  

[Allen Andreas]

Hi,

Understood. Unfortunately for the users just clicking New won't get any script logic running to copy those values, hence the UI Action suggestion. You could always create it and then have a condition on when it shows, like item = 'sys_id' ...something along those lines so that it's not always there.

Please mark reply as Helpful/Correct, if applicable.

Thanks!

[booher04]

That's a good idea.  I presented it but now we are thinking other groups will want the features for their items as well so now unless we would use a different UI action for each catalog item we couldn't go that route.