Could anyone advise me on how to aggregate multiple instances of Raise Fault policies with <FaultRule> for single Service Callout into one existence of the policy and then exit the flow process on the first occurrence of the fault? That would help error handling process become much simpler than now.
Answer by gnanasekaran · Sep 08, 2015 at 03:04 PM
sorry, not sure if understood your question.
I don't think you can aggregate Raisefault policy. If you have complex or have several conditions to be executed and raise fault accordingly I would suggest you to use the JS or python or java extensions to evaluate those conditions and set the variables accordingly, something like this - https://community.apigee.com/answers/9506/view.html
If Mukundha's comment does not answer your question, perhaps you could elaborate a little on what you mean by "aggregate multiple instances of Raise Fault policies" and "exit the flow process on the first occurrence of the fault".
@mukundha,@dino Thank you very much for the answer and follow-up. I'll check the reference you suggested to investigate if it can provide the solution we need.
lookup cache is not working as expected 1 Answer
How to retrieve key alias for SSL Info in Service Callout 2 Answers
ServiceCallout status code is populating as null for timeout or connection refused errors 3 Answers
How to set isHTTPStatusTooManyRequestEnabled to return 429 http response 12 Answers