Im exploring Windows Workflow (WF) for .NET 4.0, and there seem to be a few pieces left. From a BPM point of view, you want to have the concepts of work queues and security (user authorization).
For example, let's say you have multiple instances of a multiple workflow from several different workflows running on an application server (for example, AppFabric). Several instances are waiting for activity to be called from the client (possibly receiving WCF with content-based correlation). Clients should be able to query the server to determine which instances of the workflow (from any workflow) are waiting for input from them. This should be rights-based (preferably using Active Directory) at the activity level.
For instance:
- Workflow 1
- Activity A correlated to orderId
- Activity B correlated to orderId
- Workflow 2
- C activity related to workItemId
Workflow 1 3 , - A ( 123 456), - Activity B ( 789).
Workflow 2 1 , Activity C ( 99).
:
Workflow Activity Key
1 A orderId=123
1 A orderId=456
2 C workItemId=99
:
Workflow Activity Key
1 A orderId=123
1 A orderId=456
1 B orderId=789
( ) WF 3.x.
:
- - WF 4? , ?
- , , WF 4?
- , , ?
. SharePoint, .