MS WF 状态机工作流程和 MS CRM Dynamics 4.0
MS CRM Dynamics 4.0 整合了MS WF 引擎。 内置设计器允许创建顺序工作流程，其活动可以对 CRM 实体进行本机访问。
是否可以：
- 创建状态机工作流程 在 CRM 之外（即在 Visual Studio 中）并将其导入到 CRM 中？
- 让此工作流程访问 CRM 实体？
MS CRM Dynamics 4.0 incorporates the MS WF engine. The built in designer allows the creation of sequential workflows whos activities have native access to CRM entities.
Is it possible to:
- Create a state machine workflow
outside of CRM (i.e. in visual studio) and import it into CRM? - Have this workflow access the CRM
entities?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
可以创建无代码工作流程...
http://blogs.msdn.com/jonasd/archive/2008/01/21/Creating-a-no_2D00_code-workflow-for-CRM -4.0-with-Visual-Studio-2005-_2800_2008_2900_.aspx
并看看另一个线程...
在 Visual Studio 中编辑工作流程是否可能/是个好主意？
It is possible to create no code workflow...
http://blogs.msdn.com/jonasd/archive/2008/01/21/Creating-a-no_2D00_code-workflow-for-CRM-4.0-with-Visual-Studio-2005-_2800_2008_2900_.aspx
and take a look at the other thread...
Is is possible/a good idea to edit workflows in Visual Studio?
我不知道您的具体问题的答案，但希望这些信息能为您指明正确的方向。
WF 工作流程的“本机”格式是“.xoml”文件。 它们基本上与 XAML 文件相同，并且都只不过是 .NET 对象树的通用持久性格式。 如果您可以访问 Dynamics 设计器输出的已保存数据，则它应该采用相同的格式。 如果是，您应该能够从 Visual Studio 设计器中打开它。
这里的关键是，CRM 无疑定义了自己的一组自定义活动，您需要能够从备用设计器中引用这些活动。 运气好的话，这些会议将出现在名称明显的集会上和/或 GAC 中。
I don't know the answer to your specific question, but hopefully this information will point you in the right direction.
The "native" format for WF workflows is ".xoml" files. These are basically identical to XAML files, and both are nothing more than generic persistence formats for a .NET object tree. If you can access the saved data that is output by the Dynamics designer, it should be in the same format. If it is, you should be able to open it from the Visual Studio designer.
The key here is that CRM undoubtedly defines its own set of custom activities that you'll need to be able to reference from within the alternate designer. With any luck, these will be in assemblies with obvious names and/or in the GAC.