当选择分支触发器不触发时接收
我有一个 WF4 服务，其流程图作为根活动。它包含多个相关的接收活动和决策分支以逐步完成审批流程。接收活动工作得很好，直到我尝试使用一个活动作为选择分支的触发器。
我正在运行跟踪，因此可以看到接收已打开，并且在持久性中我可以看到关联的书签。当我发送具有接收类型的客户端消息时，它不会触发。我有一个延迟选择分支，可以正常触发，但随后的接收也不起作用。
我已经单独检查了这些接收活动，当不用作选择触发器时它们工作正常。我已经尝试过在一个序列和一段时间内进行选择，但没有区别。
我看不出我的实现与网络上的示例之间有任何区别。当接收被 pick 分支封装时，我是否缺少一些额外需要的东西？
I have a WF4 Service with a flowchart as the root activity. It contains multiple correlated receive activites and decision branching to step through an approval process. The receive activities work perfectly until I try and use one as the trigger for a pick branch.
I am running tracking so can see that the receive is opened and in the persistance I can see the associated bookmark. When I send a client message with the receive type it does not trigger. I have a delay pick branch that fires OK but then the subsequent receive also does not work.
I have checked these receive activities individually and they work OK when not used as the pick trigger. I have tried the pick within a Sequence and a While but no difference.
I cannot see any difference between my implementation and may examples on the web. Am I missing something extra required when the receive is encapsulated by a pick branch?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
PickBranch 触发器没有什么特别之处，会导致接收行为不同，因此我怀疑这是接收本身的问题。您在客户端应用程序中看到什么类型的错误？
There is nothing special about a PickBranch trigger that would cause a receive to behave differently so I suspect it is something with the Receive itself. What kind of errors are you seeing at the client application?