Understanding Try/Catch Shape behavior

Document created by mike_aronson Employee on Aug 5, 2015Last modified by dave_lesshafft on Mar 2, 2016
Version 2Show Document
  • View in full screen mode
In the July 2015 release, the Try/Catch shape was enhanced and now includes a “Failure Trigger” field.

 

You can configure the Try/Catch shape to either catch ”Document Errors” (which is by default and was the legacy design)
or you can select the new option “All Errors” which will also now catch process errors.

What should you expect if you 1 Try/Catch shape in a process, or more than 1 Try/Catch shape in a process or sub-process?

Also, what additional changes is Dell Boomi making in the August 2015 release and how will that affect your process(es)?
The following behavior is what you should expect if there is one Try/Catch shape in your process:

-- If there is one Try/Catch shape in a process and its Failure Trigger is set to Document Errors (per the picture below), then it catches only document-level errors. This is the default behavior.

-- If there is one Try/Catch shape in a process and its Failure Trigger to All Errors, then it catches both process and document-level errors.

0EM40000000brrJ

 


The following behavior is what you should expect if there is more than one Try/Catch shape in your process:

-- If a process contains one Try/Catch shape followed immediately by a second Try/Catch shape as shown in the following picture, Try/Catch Shape #1 should catch document and process errors, regardless of how its Failure Trigger is set.  Try/Catch Shape #2 should catches errors as indicated by its Failure Trigger setting.

 


0EM40000000brr4

 

-- If a process contains two Try/Catch shapes with other shapes between them, for example as shown in the following picture, theneach Try/Catch shape catches errors as indicated by its Failure Trigger setting. This is the corrected behavior in the August release If your process works differently as of the August release and if you want to revert to the pre-August behavior, change the Try/Catch Shape #1’s Failure Trigger to All Errors.

0EM40000000brr9

 


Why is Dell Boomi making these changes to the Try/Catch shape?

 

These changes enhance and correct the behavior of the Try/Catch shape.  They are being made based on two issues listed in the table below.  They are also being made based on your Feedback and popular demand to enhance this shape to allow it to catch process level errors and not just document level errors.  This changes make this shape more robust for current and future use.
AtomEnhancementPLAT-11549Try/Catch shapes separated by one or more other shapes in a process behave the same as a single Try/Catch shape.
AtomFixPLAT-9405The Try/Catch shape is not correctly catching document-level errors for subprocess errors.
4 people found this helpful

Attachments

    Outcomes