更改工作流循环活动的条件而不破坏任何现有的持久活动
我们有很多长时间运行的工作流程，这些工作流程会持久保存到数据库中，并且需要对循环条件进行逻辑更改，我们尝试将循环条件从普通变量检查更改为 函数调用，因为计算现在要复杂得多。这打破了现有的工作流程 在此更改之前保留。当我们尝试使用以下命令加载之前保存的工作流程时 新的工作流定义，加载失败并出现异常
System.Activities.ValidationException occurred
Message='LocationReferenceValue<String>' is not of type 'WaitForInput`1'. When loading this instance you must ensure that the activity with name 'LocationReferenceValue<String>' implements 'WaitForInput`1'.
Source=System.Activities
StackTrace:
at System.Activities.ActivityInstance.System.Activities.Runtime.ActivityInstanceMap.IActivityReference.Load(Activity activity, ActivityInstanceMap instanceMap)
InnerException:
是否有任何方法可以更改 WF4 中基于 XAML 的活动中 while 循环活动的条件 不破坏任何先前保留的实例？
We have a lot of long running workflows which are persisted to the database and require a logic change in the condition of a loop, we tried chaning the condition on the loop from a normal variable check to a
function call as the calculation is now lot more complicated. This breaks the existing workflows which
are persisted before this change. when we try to load the previously persisted workflow with the
new workflow definition, the loading fails with the exception
System.Activities.ValidationException occurred
Message='LocationReferenceValue<String>' is not of type 'WaitForInput`1'. When loading this instance you must ensure that the activity with name 'LocationReferenceValue<String>' implements 'WaitForInput`1'.
Source=System.Activities
StackTrace:
at System.Activities.ActivityInstance.System.Activities.Runtime.ActivityInstanceMap.IActivityReference.Load(Activity activity, ActivityInstanceMap instanceMap)
InnerException:
Is there any way to change the condition on a while loop activity in a XAML based activity in WF4
without breaking any of the previously persisited instances?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
不幸的是 WF4 没有。我们在 WF 4.5 中提供了一个称为“动态更新”的新功能，可以解决这种情况。
Unfortunately not with WF4. We have a new feature in WF 4.5 called Dynamic Update that will address this scenario.