My latest series on custom WF activities has provided a solution for managing business failures.

The BusinessFailureEvaluator<T> activity evaluates a single business failure and may result in an exception being thrown.

The BusinessFailureScope<T> activity manages multiple business failures and may result in an exception being thrown for a set of failures.

The following is a list of all the posts in this series.

• Custom Workflow activity for business failure evaluation–Part 1 – Defines the high-level design requirements for the custom activities
• Custom Workflow activity for business failure evaluation–Part 2 – Provides the base classes used to work with business failures
• Custom Workflow activity for business failure evaluation–Part 3 – Describes the implementation of the BusinessFailureExtension
• Custom Workflow activity for business failure evaluation–Part 4 – Describes the implementation of the BusinessFailureEvaluator<T> activity
• Custom Workflow activity for business failure evaluation–Part 5 – Describes the implementation of the BusinessFailureScope<T> activity
• Custom Workflow activity for business failure evaluation–Part 6 – Outlines the designer support for the custom activities

This workflow activity and several others can be found in my Neovolve.Toolkit project (in 1.1 Beta with latest source code here) on CodePlex.