Create a change request ticket based on change catalog from service catalog process using API

Hi jaredkline01 not sure I am following what you are trying to do here. Is there a reason the request would start with a service request and not just be created via the change catalog in the first place? I am not questioning that you dont have a valid use case here, just trying to understand it more. Thanks!

I have a use case like this. I have a service catalog item for end users to request something like an update to email whitelist. This requires a change, if we can create the change automatically from the ticket then I save engineering time by not having the ticket go to a engineer who then copy pastes the info from the service catalog ticket into a change ticket.

I was planning on building a process integration that goes back to api.samanage.com and opens a CR but I wondering if that will fail because its circular.

I have a use case like this. I have a service catalog item for end users to request something like an update to email whitelist. This requires a change, if we can create the change automatically from the ticket then I save engineering time by not having the ticket go to a engineer who then copy pastes the info from the service catalog ticket into a change ticket.

I was planning on building a process integration that goes back to api.samanage.com and opens a CR but I wondering if that will fail because its circular.