Flow is not triggered in RITM

manish62
Tera Contributor

Hello,

I have build one catalog item and flow (trigger is Service Catalog in flow ) and this catalog item is used by third party by using OOB Service Catalog API(https://<instance>/api/sn_sc/servicecatalog/items/<sys_id>/order_now) for submitting the request.

1- If we submit the request by SNOW portal , everything works fine.

2- If we submit the request from SNOW Rest API explorer, everything works fine.

Issue is when third party system submit the request then flow doesn't get attached in RITM no flow context, I am not sure why it's happening even i have tried with other catalog item and not working.

 

Please help me  what could be the issue and solution of this.

Thanks,

Manish

 

9 REPLIES 9

Ankur Bawiskar
Tera Patron
Tera Patron

@manish62 

did you notice any difference when RITM is created from within ServiceNow and from External API?

Did you check the RITM which gets created via API has REQ with approved state?

If yes then only flow on RITM will trigger.

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

Regards,
Ankur
✨ Certified Technical Architect  ||  ✨ 9x ServiceNow MVP  ||  ✨ ServiceNow Community Leader

Hello Ankur,

 

I didn't find difference on RITM record and yes, REQ is there with approved state but still flow is not triggered.

 

Thanks,

Manish

 

@manish62 

Make your flow "Run as" -> System user

May be the API user doesn't have sufficient access to trigger the flow

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

Regards,
Ankur
✨ Certified Technical Architect  ||  ✨ 9x ServiceNow MVP  ||  ✨ ServiceNow Community Leader

API user should have access for creating Req record based on provided  table API and that is working, for triggering flow that is something ServiceNow's functionality as i could understand , API user should have access of rest web service for creating record, is my understanding right ?

 

Thanks,

Manish

@manish62 

did you try this and check?

Make your flow "Run as" -> System user

Regards,
Ankur
✨ Certified Technical Architect  ||  ✨ 9x ServiceNow MVP  ||  ✨ ServiceNow Community Leader