Ticket #9562 (closed PLIP: wontfix)
Improve UI support for objects on multiple workflows
Reported by: | dukebody | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | Future |
Component: | Templates/CSS | Version: | 4.2 |
Keywords: | Cc: | servilio |
Description
http://plone.org/products/plone/roadmap/210
DCWorkflow allows for a chain of workflows to be specified for a type. This mostly works with Plone, but there are a few (mostly UI) warts to be fixed
Proposed by
Laurence Rowe
Proposal type
User interface
State
being-discussed
Definitions
Motivation
Multiple workflows allow for modelling of complex business processes. Assumptions
Proposal
- Modify content_status_modify to take an optional workflow_id parameter, to be passed as wf_id to portal_workflow.doActionFor. This removes the requirement to transitions to be uniquely named across multiple workflows.
o CMFPlone o plone.app.contentmenu o plone.app.kss
- Show workflow history for each workflow
o plone.app.layout
Implementation
Deliverables
Risks
- Modify content_status_modify
o If a user has customised this script it may break. Only pass workflow_id if more than one workflow in a type's chain.
- Show workflow history for each workflow
o Will break view customisations
Progress log
- Modify content_status_modify
o not yet started. About 1 hours work.
- Show workflow history for each workflow
o see attached patch
Participants
Laurence Rowe
Change History
Note: See
TracTickets for help on using
tickets.
PLEASE READ THIS AND RE-OPEN VALID PLIPS!
As we launch the new PLIP process we'd like to see which PLIPs:
If this PLIP should still be considered for future releases of Plone please do re-open this ticket and assign an appropriate milestone. If it should be considered for the next release of Plone, use the 4.2 milestone. Also be sure to update the PLIP description, requester, owner, etc. and include a comment detailing recent progress and new plans. We will use all these details in the new continuous PLIP process.