唤醒顺序工作流程服务

Question

我需要能够“唤醒”顺序工作流服务-这个概念以前在状态机中起作用，所以我不理解为什么它在序列中不起作用。 下面是工作流程的图片。

此工作流程用于编排其他工作流程服务。 它实际上需要永远运行-但是我们需要能够将其轻柔地关闭。 以前，我在状态机中实现过相同类型的事情，延迟是一次转换的触发，而接收是另一个转换的触发。 只要第一个提到的转换未运行，我就可以让Receive接收消息并转换到最终状态。 正如您所看到的，在这里我要做的只是将布尔值设置为False，指示While循环应退出，因此工作流将终止。

请帮助我了解为什么这不起作用。

谢谢大家！

编辑诊断输出

32: Activity [1] "Main Sequence" scheduled child activity [4] "While"
33: Activity [4] "While" is Executing
{
    Variables
        continueRunning: True
}
34: Activity [4] "While" scheduled child activity [6] "VisualBasicValue<Boolean>"
35: Activity [6] "VisualBasicValue<Boolean>" is Executing
36: Activity [6] "VisualBasicValue<Boolean>" is Closed
{
    Arguments
        Result: True
}
37: Activity [4] "While" scheduled child activity [8] "Pick"
38: Activity [8] "Pick" is Executing
39: Activity [8] "Pick" scheduled child activity [9] "Soft Exit Branch"
40: Activity [8] "Pick" scheduled child activity [26] "Process Branch"
41: Activity [26] "Process Branch" is Executing
42: Activity [26] "Process Branch" scheduled child activity [42] "Delay"
43: Activity [42] "Delay" is Executing
{
    Arguments
        Duration: 00:01:00
}
44: Activity [9] "Soft Exit Branch" is Executing
45: Activity [9] "Soft Exit Branch" scheduled child activity [14] "Soft Exit Sequence"
46: Activity [14] "Soft Exit Sequence" is Executing
{
    Variables
        __handle1: System.ServiceModel.Activities.CorrelationHandle
}
47: Activity [14] "Soft Exit Sequence" scheduled child activity [21] "Soft Exit"
48: Activity [21] "Soft Exit" is Executing
{
    Arguments
        CorrelatesWith: System.ServiceModel.Activities.CorrelationHandle
        Parameter0: System.ServiceModel.Activities.CorrelationHandle
}
49: Activity [21] "Soft Exit" scheduled child activity [21.1] "Sequence"
50: Activity [21.1] "Sequence" is Executing
{
    Variables
        RequestMessage: 
        ReceiveNoPersistHandle: System.Activities.NoPersistHandle
}
51: Activity [21.1] "Sequence" scheduled child activity [21.6] "InternalReceiveMessage"
52: Activity [21.6] "InternalReceiveMessage" is Executing
{
    Arguments
        CorrelatesWith: System.ServiceModel.Activities.CorrelationHandle
        noPersistHandle: System.Activities.NoPersistHandle
        Parameter0: System.ServiceModel.Activities.CorrelationHandle
}
53: WorkflowInstance "Main Sequence" is Idle
54: WorkflowInstance "Main Sequence" is Persisted
The thread '.0' (0x1fa4) has exited with code 0 (0x0).
The thread 'DebuggerThread:Soft Exit Branch.1' (0x13b4) has exited with code 0 (0x0).
55: WorkflowInstance "Main Sequence" is Unloaded

Answer 1

您应该获得一些跟踪数据-这将有助于您了解发生了什么。 请参阅使用诊断日志记录对工作流服务进行故障排除

Answer 2

此工作流随Visual Studio Framework 3.5一起提供。可以使用Framework 4.0中的活动库或使用工作流控制台应用程序来完成类似的活动。

我只是想添加它，因为很多人说他们不愿意在Visual Studio中看到顺序工作流。尽管我们可以仅使用Visual Studio来使用它来创建工作流（没有SharePoint / WSS / MOSS / SP2010或Designer）。 。但是，这不是一个好的IDEA，因为它需要对OOB项的外观进行开发工作。最好的方法应该是使用SPD。或使用MOSS的工作流功能。

仅使用VS也会创建审批工作流是痛苦的。.我很快将创建一个粘贴。

Answer 3

我已经解决了问题。 这个问题与相关性有关，我应该知道得更多。 每个“接收/发送-应答”序列都有自己的本地__handle1变量，用于“发送-应答”相关句柄。 但是，我试图使用它来关联消息，以使用SoftExit唤醒序列。 我创建了一个新的关联句柄__liveHandle，在离开开始序列时进行了初始化，然后在“软退出序列”中对该句柄进行了关联-已解决。

谢谢@RonJacobs！