SharePoint world of ECM and Information Management

.NET Tips: WorkFlow

back to content

INFO:

• Existed v1 version doesn't support de-serialization of activities which were added dynamically to the existed static activity. >>
• All actions in WF go through a queue and waits for the background thread to dequeue it and do it. Unfortunately, the queue is only processed in between activities executing. So, if you activity can may never ends. It this case consider using async activities. >>
• Try to avoid usage DelayActivity as a timer in complex workflows and inside StateActivity. The reason is that changing timer doesn't suppoted out-the-box, DelayActivity must be the first in EventDriven activity and can't be compositite in that case. >>
• WF DelayActiviy Timeout has a bug and limited only to 47 days. It's fixed in .NET 3.5 WF >>
• You can't change the TimeOut of DelayActivity after it was started.

back to content