Learning Curve…

Archive for November 2011

When we call the start workflow function, we can pass as name/value pairs using the dictionary object.

Advertisements

Windows Workflow Foundation gives developers a declarative way to create workflows by using XAML.  These markup files are Stored with XOML (Extensible Object Markup Language) extension.  Markup file can also have code behind. The whole concept of having code behind for XOML file is to separate the presentation from logic files.

One of the best thing with Markup is we can change the sequence just by changing the XOML file we do not need to compile the whole application again.So using XOML we can serialize workflows.

Exception handling in Workflow is somewhat different than how we do in normal .NET application. We can handle exceptions in Workflow using following steps  :-
1 – We have small tab, which says view exceptions. If you click on view exception, you will be redirected to a workflow design only for exception .
2 – This is the workflow which will execute in case we have exceptions. We can put a code activity, which points to a method where we can have our exception functions and/or error messages.

We can define conditions in workflow by using conditionedActivitygroup.

If the workflow is very rigid then you go for sequential workflow and if the workflow is dynamic then go for State machine workflow.

For instance you have placed an order and the order will not pass until your supervisor approves is a rigid flow. Because your order has to be approved by, a supervisor or else it will not be approved. But what if your order moves from one place to other place. For instance, it moves from approval to waiting and then clarification a state machine workflow model is more appropriate.

There are two basics type of workflow Sequential Workflow and State machines workflow.

A sequential workflow has clear start and finish boundaries. In sequential execution, one task is executed after other. Sequential workflow is more rigid in format and execution path has a determistic nature.

A State machine workflow is more dynamic in nature. Workflow has states and the state waits for
events to help it move to next state. In State machine execution path is undetermestic nature.

Hard work — Less application of brain with high physical effort.

Smart work — Full application of brain with less physical effort.


Author

Learning days (Calendar)

November 2011
M T W T F S S
« Oct   Dec »
 123456
78910111213
14151617181920
21222324252627
282930  

Knowledge Bank (Archives)

I am on Twitter

Blog Stats

  • 510,411 hits

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 43 other followers

%d bloggers like this: