Exception Handler for Method Calls inside ADF Task Flows with Fragments

In regular case, when JboException is thrown from the Model, it is rendered in UI within popup component automatically. This works fine, when we are calling operation bindings directly. However, if operation is called through ADF task flow Method Call - JboException is being catched by Controller layer and is rendered differently. Exception handling for ADF task flows with pages can be done slightly differently, I will explain it in my next post.

Download sample application - MethodCallExceptionHandler.zip. This sample app contains one customer method in Application Module implementation class, where JboException is being thrown:

This method is exposed to the ViewController through Data Control:

ADF task flow Method Call activity is implemented to invoke processData() method, which throws JboException:

On runtime, when JboException is encountered from Method Call activity, we are getting browser error:

This can be avoided by defining single ADF task flow Template with only one activity - Method Call marked as error handler:

In the case, when we have ADF task flow with fragments, there is no need to implement error handler method - exception is handled and popup will be rendered automatically. Only what we need to do is to define error handler ADF task flow activity as shown in the screenshot above.

In order to define error handler method activity ones, we are using ADF task flow Template. All ADF task flows, where we want to handle JboExceptions for Method Calls should be based on that template:

In a case when JboException will happen, user friendly popup with error text will be rendered to the user: