Plone工作流程的圣杯 [英] The Holy Grail of Plone workflow

问题描述

我们正在将Plone CMS实施为ISO9001文档的存储库.

We are in the process of implementing a Plone CMS as a repository for ISO9001-documents.

ISO要求一定数量的日志记录，任何熟悉该标准的人都可能知道:-)

ISO demands a certain amount of logging, as anyone familiar with the standard probably knows :-)

出于灵活性的考虑，我们希望以没有特定顺序的方式合并

For the sake of flexibility we would like to incorporate, in no specific order:

• 新的内容类型:合并企业中可能出现的不同文档所必需的
• 版本控制:显示我们的文档始终是最新的，并显示与同一文档的先前版本相比进行了哪些更改
• 工作副本支持:使已发布"的文档在编辑过程中保持在线状态
• 更复杂的工作流程:考虑ISO规定的审核流程
• 不同文档的工作流程不同:由于工作流程取决于文档的类型.

因此，工作流优化的圣杯应该是(如果我错了，请纠正我):

Therefore, the holy grail of workflow optimisation should be (and please correct me if I'm wrong):

• 内容类型的灵活性
• CMFEdition(嵌入在Plone中)进行版本控制
• 迭代获得工作副本支持
• 用于新工作流程的plone.app.workflowmanager
• Products.CMFPlacefulWorkflow用于根据不同文档的不同工作流程

问题在于不同产品的集成:

The problem is the integration of the different products:

• 如何使版本控制与Dexterity一起使用?
• 如何在此基础上添加工作副本(保持必要的版本控制)?
• 以及如何使您闪亮的新工作流(对于工作流管理器而言，UI较大)在版本控制和工作副本中都能很好地发挥作用.

我搜索了Google领域，并已经找到以下链接:

I scoured the google-realm and already found these links:

• 工作副本和工作流程: http://plone .org/products/iterate/documentation/how-to/working-copy-workflow-customization
• 灵活性和版本控制: http: //plone.org/products/dexterity/documentation/how-to/adding-versioning-to-dexterity-content-types

• Working copies and workflows : http://plone.org/products/iterate/documentation/how-to/working-copy-workflow-customization
• Dexterity and Versioning: http://plone.org/products/dexterity/documentation/how-to/adding-versioning-to-dexterity-content-types

我们还签出了:

• Archetypes内容类型的版本控制: http://plone.org/documentation/manual/developer-manual/archetypes/appendix-practicals/enabling-versioning-on-your-custom-content-types

所有这些都已安装并配置...

which are all installed and configured...

但是，我的新内容类型不允许签出/签入(迭代产品)，并且在历史视图中也没有针对同一内容类型跟踪版本/更改.

However, my new content type does not allow for checkout/checkin (Iterate product), and neither are versions/changes tracked in the history-view for this same contenttype.

他们遵循的魔术顺序还是我错过了某些东西(或者很多-更有可能)?因为在我看来，如果所有这些产品都可以开箱即用"地工作，那么这是万能的工作流程的万能解决方案...

Is their a magical sequence to follow or am I missing something (or alot -which is more likely)? Because if all these products were to work "out of the box" in my opinion this is a catchall solution to all things workflow...

附加信息2012/04/17:如thet所述，堆栈同时包含两者

addition 2012/04/17: As remarked by thet, the stack is completed with both

• 敏捷的行为版本: http://pypi.python.org/pypi/plone. app.versioning行为
• 敏捷性的过渡行为: http://pypi.python.org/pypi/plone. app.staging行为

• versioningbehavior for Dexterity: http://pypi.python.org/pypi/plone.app.versioningbehavior
• stagingbehavior fro Dexterity: http://pypi.python.org/pypi/plone.app.stagingbehavior

推荐答案

您需要使用plone.app.stagingbehavior(http://pypi.python.org/pypi/plone.app.stagingbehavior)，该链接链接Iterate/CMFEditions为敏捷类型.不确定您的版本问题.

You need to use plone.app.stagingbehavior (http://pypi.python.org/pypi/plone.app.stagingbehavior), which links Iterate/CMFEditions to Dexterity types. Not sure about your versioning issues.

这篇关于Plone工作流程的圣杯的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！