copy code,drag or close
Introduction to Windows Workflow Foundation (WWF)
Two aspect to help the introduction along are found from looking at the
Architecture
and the
Extensibility
of what is now known as the Windows Workflow Foundation.
Workflow has often been formerly presented via flowcharts.
Flowcharts can be used at a number of levels, for simultaneous activities involved in some technical process up to more business based activates involving people.
Introduction to Windows Workflow Foundation (WWF)
Two aspect to help the introduction along are found from looking at the
Architecture
and the
Extensibility
of what is now known as the Windows Workflow Foundation.
Workflow has often been formerly presented via flowcharts.
Flowcharts can be used at a number of levels, for simultaneous activities involved in some technical process up to more business based activates involving people
Traditional flowcharts describe activity flow as a seqence such as the flow reaching a decision box and brancing left or right based on the answer
State transition models are another popular way of representing the organizing of activities; they define states and the rules that govern the transition between states.
A typical example might be an insurance companies’ activities for approving a claim for payment.
Such models tend to be a little more ad hoc and more easily represent real business world situations where everything is not determined in advance.
WWF is a runtime engine which must be hosted within a host server or application, it is not application itself but there is a visual designer
A fundamental point is “an activity can be made up of several other activities”, this means that certain “base” activities are likely to re-used when creating a workflow.
The Components as delivered to developers include a base activity library, used for building custom activity libraries, a runtime engine to instantiate workflow instances and the messaging between different states.
Using the insurance example we can say some states might be unapproved, initial approval, final approval, disapproved. The last component is best described as the runtime services, those that allow flexible extensions.