#130: Integration of PloneWorkflowTransitions in to Plone
- Contents
- Proposed by
- Riccardo Lemmi
- Proposal type
- User interface
- State
- being-discussed
Motivation
Some use cases require, when a user try change the state of a content, to redirect the user to a form, currently the only way to do it is to customize 'global_contentmenu.pt'.
Proposal
The product "PloneWorkflowTransition" customize the 'global_contentmenu.pt', so that the url showed in the 'state' action be the "Display in actions box URL" attribute and rewrite all the old urls in the workflow definitions to be the real.
Implementation
To have this feature integrated in Plone it is needed to integrate 'global_contentmenu.pt' of "PloneWorkflowTransition" and to rewrite all the workflow transition definitions in PloneWorkflow.py and FolderWorkflow.py.
Risks
A product like "PloneWorkflows", or in general products installing new definitions of workflows require to rewrite the actbox_url to the real url, for example in plone_workflow there is:
actbox_url = "%(content_url)s/content_publish_form"
this should be transformed in:
actbox_url = "%(content_url)s/content_status_modify?workflow_action=publish"
to work correctly.
Participants
Riccardo Lemmi, Vincenzo Di Somma
Re: isn't this just configuration
I don't know very well generic setup configuration, but it is not a question of configurantion of workflows only, because at least global_contentmenu.pt should be rewrite to read the actbox_url attribute.
Anyway I will check this possibility.
This is key
This is one of the major features in Plone Workflow I find lacking. Because most workflows are meaningless without associated actions (Workflow scripts, variables), it is important for the user to be able to interact with the workflow transition.
isn't this just configuration