New Request has required approvals that are not allowing the Catalog Tasks to kick off

[Danny Barker]

I am in the process of creating several request flows using Flow Designer.  After activating the flows and creating a few test Requests, we see that the Catalog tasks are not kicking off.  We have no approvals set in the flow but we however see that the Request form has approval fields as seen below. 

Is there a way to bypass this so that our Catalog Tasks will open?  If this is an OOB feature for Service Catalog, is there a way to add a subflow to the request flow that automatically marks these as approved? 

Any help would be greatly appreciated!

[jonsan09]

Would you be able to share what your flow looks like?

[Danny Barker]

Sure thing.  I had a more complex flow when I first discovered this was happening.  I then created a basic hardware flow only containing a trigger and one action as seen below for testing. ( with no approvals )

Once the Request is created for the hardware item that uses this flow ( for Testing ) You can see, the fields are displayed for Approval below 

To confirm the catalog tasks is not firing off, I opened the RITM 

This seems to be something OOB with Service Catalog as even added a Hardware Item with no flow attached and still get the required approval field on the Request form.  

I also want to add that this is happening on our company test instance.  On my own dev instance I can recreate the exact same flow, open a request, and confirm that the request is automatically approved.  

The only thing we can see that is different is that on our company test instance with the issue is t hat we recently did a zboot and removed our demo data. 

[jonsan09]

You'll want to check the 'Cascade Request Approval to Request Item' business rule and 'Service Catalog Request' workflow on the sc_request table. I believe both of those are required to update the Request item (sc_req_item record). You'll want to double check the catalog item to make sure there is only a flow attached to it and not any other workflows or execution plans

[Danny Barker]

Thank you for the recommendations.  I checked the Business rule 'Cascade Request Approval to Request' as I found a few other posts pointing to that as well.  The settings look correct and matched up to my personal dev instance that is not experiencing the issues.  I even temporarily deactivated the rule for testing and it made no difference.  

I ended up looking at the Approval Rules.  On My personal dev instance, there was a rule called   "Catalog Request Default Approval"  This rule as seen below, was targeting the sc_request table and the conditions were set for less than $1000, and "Set State" field was Approved.  I added the Approval rule on our company test instance.   I was however prompted to turn on the Approval Engine on for Request.   Once doing so,  the two fields on the request form are now defaulting to Approve.  

Please let me know your thoughts.  If there is possibly another Best Practice way to achieve this.