Catálogo de publicaciones - libros

WF provides a flexible rules evaluation engine that you can use when developing applications. Rules are an alternate way to implement business requirements and they complement the other mechanisms that are provided with WF. A is simply a declarative statement about your data. Within a rule, you declare a condition that you wish to evaluate at runtime. If the condition evaluates to true, one or more actions that you define are executed. A rule also permits you to define actions to execute when the condition evaluates to false. The rules support in WF includes a rules editor that allows you to declare individual rules and group them together into rule sets.

The focus of this chapter is exception and error handling. WF provides a way to declaratively handle exceptions within the workflow model. While this doesn’t completely eliminate the need to handle exceptions within your code, it does allow you to declare some cleanup logic within the workflow model, enabling easier changes to the logic as it becomes necessary.

The focus of this chapter is dynamic workflow updates. WF provides the ability to make dynamic changes to the structure of a workflow instance. Structural changes might include adding or removing activities based on updated business requirements. When updates are applied to a workflow instance, they only affect that one instance. All other instances of the same workflow, current and future, use the original workflow definition.

The focus of this chapter is workflow tracking. is a built-in mechanism that automatically instruments your workflows. By simply adding a tracking service to the workflow runtime, you are able to track and record status and event data related to each workflow and each activity within a workflow.

The focus of this chapter is web services and the use of workflows from ASP.NET applications. WF provides support for web services in a number of ways. You can develop a workflow and expose it to clients as a web service. You can also invoke a web service declaratively from a workflow. WF also permits you to host the workflow runtime and invoke workflows from an ASP.NET client application.

The focus of this chapter is the use of workflow markup and serialization. WF provides several authoring modes that you can use when defining the workflow model. This chapter discusses those authoring modes, spending most of the time demonstrating the use of workflow markup. Workflow markup is a serialized representation of the workflow model that is saved as a .xoml file.

The focus of this chapter is hosting the workflow designers in your own application. You might need to do this if you want to provide someone other than a Visual Studio developer with the ability to modify workflow definitions. Hosting a customized version of the workflow designers goes hand in hand with no-code workflows. The main advantage of using no-code workflows is that they are distributed in a form that is easy to modify (.xoml markup files). A customized workflow designer provides a way to modify those markup files.