Search This Blog

Thursday, November 13, 2008

Important Points On Workflows :

1. ability to change a business process on the fly
2. Any application that implements a long-running process is a natural for workflow. Processes that interact with people, who can take hours or days to respond, are one important instance of this. For example, building a document approval application around a workflow would make good sense.
3. An ASP.NET application that displays pages to its users might use a workflow to control the order in which those pages are shown. Doing this can make it easier to change the page flow without changing the pages themselves, as well as cleanly separating the application’s user interface from its controlling logic.
4. WF can make the application faster to build, quicker to change, and easier to customize.
5. The ability to maintain state throughout the workflow’s lifetime. Especially when people are involved, as with the manager in this example, a workflow can take a long time to complete. (What if the manager has left for the day, or is on a two-week vacation?) Building scalable systems also requires a way to deactivate the workflow and store its state persistently, then reactivate it and load that state when the next step can be executed.
6. The purpose of WF is not to be a complete workflow solution for Windows. Instead, the goal is to make it easier for software developers to create workflow-based Windows applications.
7. workflow consists of a group of activities­­­
8. The workflow acts as a container for these activities, providing a way to control their lifecycles and order of execution.
9. WF provides two built-in workflow types: sequential workflows, capable of executing activities in a pre-defined pattern, and state machine workflows, capable of responding to external events as they occur. Both rely on the same runtime environment, and both can use the same custom activities.
10. Framework 3.5. In this version, it’s straightforward to use WF and WCF together to create workflow-enabled services.
This combination depends on two new WF activities:

Sequence Workflows are Sequence driven workflow
State Machine Workflows are Event Driven workflow(External Events are raised by external user)
Post a Comment

Popular Posts