
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-03-2019 08:29 AM
I have a simple happy path scenario for ordering a Service Catalog Item and I'm wanting my Flow Designer flow to be triggered. The problem is that my Flow is NOT being triggered. I can easily test this within Flow Designer and it works perfectly but it doesn't work when ordering a SC request item.
It appears the root cause is a business rule called "Start FlowDesigner Flow." It requires the stage to be equal to request_approved upon an update scenario. But, in my case the request item is being created brand new (insert) and the default value in the state field is "waiting_for_approval." More detail is below showing all the steps I've verified.
How do I get my Flow to trigger successfully in this scenario?
I've checked off all the items I'm supposed to do to make this happen. For example,...
- Activate Flow Designer support for Service Catalog. DONE.
- Create a flow with a Service Catalog trigger. DONE.
- Create a Service Catalog Request and make sure the Flow is selected as the process engine as well as workflow and Execution Plan is empty. DONE.
Images below show each step I've taken. Any help is greatly appreciated.
Below image shows I have a simple flow which I can test successfully inside Flow Designer.
Below image shows my Catalog Item that is attached to my "Simple Flow Test" flow.
This is a test of actually ordering the Request Item.
This shows my requested item is set to "waiting_for_approval" by default for the stage.
Finally, here is the business rule that may be the problem (at least the way I'm intepreting). Notice it triggers only on update and then the stage must be equal to "request_approved." My requested item surely won't be "request_approved" initially as I wanted to setup the approvers inside my Flow (which I cannot even get my flow to trigger).
p.s., there is another post very similar to mine that doesn't fully explain how to resolve this predicament.
Solved! Go to Solution.
- 14,953 Views

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-06-2019 08:27 PM
Here is the final solution that resolves this. I needed to add a business rule that triggers on insert of sc_request. However, the solution cannot simply execute for all sc_request insertions. Rather, I only wanted it to trigger for my specific sc_request. Therefore, my business rule setup is listed below. Notice that I'm specifically looking for attached sc_req_item records that have the exact number of variables as well as the exact named variables I'm looking for. If it matches, then the script will update the sc_request.approve to approved. Hopefully this helps others if they are struggling.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-05-2021 04:53 AM
Hi Laxmi,
this BR is triggering on update, please make it run on insert also along with condition change. then flow will be triggering on RITM creation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-16-2022 11:24 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-15-2020 11:02 AM
Hi,
anyone was able to solve the issue reported by
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-05-2021 04:54 AM
Hi Costa,
This BR is triggering on update, please make it run on insert also along with condition change. then flow will be triggering on RITM creation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2022 07:09 PM
That does not work every time once the Flow is published, however; it works every time when it's being tested.
The message rec'd is NullPointerException. I even tried to Wait a few seconds as the 1st step in the workflow, but I still keep getting the error. I end up running a Test for the workflows that have issues (which happens often).
I opened a case with ServiceNow & they told me to revert the Business Rule Start FlowDesigner Flow back to OOB, which is only Insert & stage is request_approved.
I don't understand why they would set the rule up this way if we need to workflow to trigger the appropriate approval; it defies logic in my head.
Does anyone else know why they would do that?