Flow Designer Trigger for sc_req_item Table Not Available in Scoped App

[wilsonpaulraj]

I'm developing a scoped application intended for publishing on the ServiceNow Store via the Technology Partner Program (TPP).

My use case involves integrating with an external system when a new item is requested through the Service Catalog. Naturally, I want to trigger a flow when a record is created in the sc_req_item table.

However, while building a Flow Designer Flow within my scoped app, I noticed that the sc_req_item table does not appear in the list of available tables for the Trigger section.

---

What I've tried / observed:

• The sc_req_item record is created in the Global scope, even though my flow is in a scoped app.

• Tables like sc_request are available in the trigger list, but they are not suitable because they don’t allow me to act directly on sc_req_item data.

---

My goals:

1. Build a reliable trigger that works when sc_req_item records are created.

2. Ensure the logic remains within the scoped app, to keep it portable and ready for Store publication.

---

My questions:

1. What is the recommended approach for triggering logic (e.g., Flow or BR) on sc_req_item creation from within a scoped application?

2. Is there a way to enable sc_req_item in Flow Designer triggers?

---

Any insights or recommended approaches would be greatly appreciated. Thank you in advance!

[Ankur Bawiskar · Accepted solution]

@wilsonpaulraj 

you cannot create flow on sc_req_item table as it's not allowed by ServiceNow.

You can use business rule and handle the script there or call a subflow and handle the logic there

[sc_req_item] Table not available on Trigger of Process Automation Designer 

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

[wilsonpaulraj · Accepted solution]

Thank you for the clarification, Ankur! 🙌
That makes sense regarding sc_req_item not being available as a trigger in Flow Designer or Process Automation Designer.

However, I’m facing a related issue and would appreciate your guidance:

I’m building a scoped app and I want to trigger an integration flow when a record is created in the sc_req_item table.

Since sc_req_item is in the global scope, and my app is scoped, I cannot create a Business Rule on it within my scoped app. And creating a Business Rule directly in the global scope defeats the purpose of packaging and distributing a standalone app.

My questions is how should i trigger a scipt when a record is created in the sc_req_item table?

Should I:

1. Create a global Business Rule and have it call a Script Include/subflow from the scoped app? If so, how do I safely reference a Script Include from a different scope?

2. Or should I rethink the architecture — maybe use a different table or an intermediary table to mirror requests?

Any guidance on Store-safe architecture for this kind of integration would be super helpful!

Thanks again,
Wilsonpaulraj

[Ankur Bawiskar · Accepted solution]

@wilsonpaulraj 

what's the purpose of triggering an integration and why record is created in RITM table?

Record in RITM is usually created when someone raises a request from service catalog or from portal.

Someones we do need to ship separate update sets along with the store app as not everything can be captured in same scope.

I did follow this practice in the past for scoped app.

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

[Ankur Bawiskar · Accepted solution]

@wilsonpaulraj 

you cannot create flow on sc_req_item table as it's not allowed by ServiceNow.

You can use business rule and handle the script there or call a subflow and handle the logic there

[sc_req_item] Table not available on Trigger of Process Automation Designer 

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

[wilsonpaulraj · Accepted solution]

Thank you for the clarification, Ankur! 🙌
That makes sense regarding sc_req_item not being available as a trigger in Flow Designer or Process Automation Designer.

However, I’m facing a related issue and would appreciate your guidance:

I’m building a scoped app and I want to trigger an integration flow when a record is created in the sc_req_item table.

Since sc_req_item is in the global scope, and my app is scoped, I cannot create a Business Rule on it within my scoped app. And creating a Business Rule directly in the global scope defeats the purpose of packaging and distributing a standalone app.

My questions is how should i trigger a scipt when a record is created in the sc_req_item table?

Should I:

1. Create a global Business Rule and have it call a Script Include/subflow from the scoped app? If so, how do I safely reference a Script Include from a different scope?

2. Or should I rethink the architecture — maybe use a different table or an intermediary table to mirror requests?

Any guidance on Store-safe architecture for this kind of integration would be super helpful!

Thanks again,
Wilsonpaulraj

[Ankur Bawiskar · Accepted solution]

@wilsonpaulraj 

what's the purpose of triggering an integration and why record is created in RITM table?

Record in RITM is usually created when someone raises a request from service catalog or from portal.

Someones we do need to ship separate update sets along with the store app as not everything can be captured in same scope.

I did follow this practice in the past for scoped app.

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

[wilsonpaulraj]

Hello @Ankur Bawiskar 

Thank you again

To answer your question, the goal is to build a scoped application that automatically pushes service catalog requests to an external application used by the client to manage all IT service requests centrally.

The client uses another system as a unified service management platform, so whenever a request is raised through the ServiceNow catalog, they want it to be instantly pushed to their external application. For this:

• I created a Business Rule on sc_req_item

• The Business Rule triggers a Script Action, which sends an Outbound REST message

• This message goes to a middleware service, which handles the downstream processing
  
  

  Since sc_req_item is a global table, and my application is scoped (intended for the ServiceNow Store), I’m not allowed to define a Business Rule on it within my scoped app.

  You mentioned sometimes it's necessary to ship an additional update set outside the store app. I wanted to confirm if that's the best approach in this case.

  Would it be acceptable to include a separate update set with a global-scope Business Rule that calls a Script Include or Flow in the scoped app?
  
  
  Thankyou
  Wilsonpaulraj