Flow Designer not Triggering for Service Catalog Request Item

Todd O
Tera Guru

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,...

  1. Activate Flow Designer support for Service Catalog. DONE.
  2. Create a flow with a Service Catalog trigger. DONE.
  3. 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. 

find_real_file.png

Below image shows my Catalog Item that is attached to my "Simple Flow Test" flow.

find_real_file.png

 

This is a test of actually ordering the Request Item. find_real_file.png

This shows my requested item is set to "waiting_for_approval" by default for the stage.

find_real_file.png

 

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). 

find_real_file.png

find_real_file.png

p.s., there is another post very similar to mine that doesn't fully explain how to resolve this predicament.

 

1 ACCEPTED SOLUTION

Todd O
Tera Guru

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.

find_real_file.png

find_real_file.png

View solution in original post

21 REPLIES 21

LAXMI TODAKAR2
Tera Contributor

Hello @Todd O ,

instance version: Orlando

I am configuring flow designer in catalog item, As you can refer the screenshots, but while creating item request, it is not triggering the flow designer.

Analyzed points:

 1) All plugins related to flow designers are installed.

2) Business rule as mentioned above "Start FlowDesigner Flow", I changed the condition and checked, it didn't workout.

find_real_file.png

 

 

find_real_file.png

 

Please help me to solve the issue.

Thanks,

Laxmi

I think you can forcefully start flow designer from business rule.

Please go through below URL to see how flow designers can be force started.

 

https://developer.servicenow.com/dev.do#!/learn/learning-plans/orlando/servicenow_application_developer/app_store_learnv2_flowdesigner_orlando_scripting_with_flows_subflows_and_actions

Thanks rajneeshbaranwal, for your response.

I will try this code, will let you know the response.

 

Thanks,

Laxmi

 

In your service catalog item, did you also specify which Flow is associated with the item? See image below. 

find_real_file.png

Hello @Todd O ,

 

Please find the screenshot, I am configuring flow in catalog item.

find_real_file.png

Let me know any findings.

Thanks,

Laxmi