Use PDIs? Take our 5-minute survey to help shape the PDI roadmap.

Service Catalog trigger not firing on catalog order (PDI) — sc_req_item unavailable as Record trigge

Lechylech
Mega Contributor

I'm building a flow in Workflow Studio on my PDI and my Service Catalog trigger never fires when the catalog item is ordered.

 

Setup:

  • Flow with a Service Catalog trigger (tried both no condition and scoped to the item)
  • Catalog item has an input variable, the flow calls a subflow that reads it
  • Catalog item's Process Engine Flow field is empty (trigger is meant to drive it)

Symptom:

  • On ordering the item, the  "Service Catalog Request" and "Request Management Approval" flows fire and complete (visible in sys_flow_context), but my custom flow never appears in the context list at all
  • The flow works correctly when run manually via Test against a Requested Item, so the logic is fine, only the auto trigger fails
  • I tried switching to a Record Created trigger instead, but sc_req_item (Requested Item) doesn't appear as a selectable table in the trigger's table picker (only sc_request and sc_request_watcher show)

Questions:

  1. Why would a Service Catalog trigger fail to fire on a catalog order?
  2. Is there a property or setting required to enable Service Catalog / catalog-item triggers?
  3. Why is sc_req_item unavailable as a Record trigger table, and how do I enable it?

Has anyone seen this, any fixes? Is this a limitation of PDI?

 

Thanks in advance.

1 ACCEPTED SOLUTION

Ankur Bawiskar
Tera Patron

@Lechylech 

The flow attached to catalog item should be triggered provided

1) the flow is published and linked to that item

2) your REQ is approved which is the trigger of the catalog item flow

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

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

View solution in original post

4 REPLIES 4

AndersBGS
Tera Patron

Hi @Lechylech 

 


Please share a snip of your trigger configuration, by doing so it will be much easier to help you.

 

If my answer has helped with your question, please mark my answer as the accepted solution and give a thumbs up.

Best regards
Anders

Rising star 2024
MVP 2025
linkedIn: https://www.linkedin.com/in/andersskovbjerg/

Thanks for taking a look. Screenshots attached.

 

  • My Service Catalog trigger config (image 1): the only option under the trigger is where to run the flow, there's no field to bind it to a specific catalog item. Is that expected, or should there be a catalog item selector here?
  • Proof trigger doesn't work (image 2): sys_flow_context after ordering my item at 18:05. The Service Catalog Request and Request Management Approval flows fire and complete, but my flow "MTR LAPS Retrieval" is absent. The only run of at 17:38 was a manual Test, which works fine, so the logic is sound, only the auto trigger fails
  • Record trigger workaround blocked (image 3): I tried switching to a Record Created trigger, but sc_req_item (Requested Item) doesn't appear as a selectable table, only sc_request and sc_request_watcher show.

Should the Service Catalog trigger have a way to scope to a specific catalog item, and could its absence be why mine isn't firing?

 

Why is sc_req_item unavailable as a Record trigger table, and how do I enable it?

 

Service Catalog trigger configurationFlow execution contexts after orderingRecord Created trigger, table pickerCatalog item Process Engine + record

Ankur Bawiskar
Tera Patron

@Lechylech 

The flow attached to catalog item should be triggered provided

1) the flow is published and linked to that item

2) your REQ is approved which is the trigger of the catalog item flow

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

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

Lechylech
Mega Contributor

Thanks! It seems linking the flow via the process engine in the catalog item was the fix, I thought I only had to link this when setting up the flow itself.