Workflow policies for CMF and Plone
Project description
Overview
Placeful Workflow is a Plone product that allows you to define workflow policies that define content type to workflow mappings that can be applied in any sub-folder of your Plone site:
When you access the root of your site, you will see a new action in the workflow state drop-down menu called “policy”. Click on the “policy” link.
The next page will let you add a policy to your folder by clicking on the “Add Workflow policy” link. Click on “Add Workflow policy”.
Now you have a workflow policy in your site, and you can set the workflow policies for this folder and below.
We didn’t add any workflow policies, so you don’t have a choice of different workflow policies yet, so the default workflow policy will be taken both for the folder and below.
Installation
Use Site Setup -> Add-on Products panel to install
Now you can define and apply local workflow policies through the Plone Interface.
Usage
Now, let’s define a new workflow policy:
Access “Site Setup” and click on “Placeful Workflow” in the “Add-on Product Configuration” section.
Enter the name “my_policy” in the “New policy” field, and click on “add”.
Now you have a new policy. Enter the title “Example policy” and the description “This is an example policy”.
Change the workflow for the content type “Folder” from “folder_workflow” to plone_workflow”, and click on “Save”. Now all your content types should use the “plone_workflow”.
Let’s test the new workflow policy for “Folders” at the root of our site:
At the root of the site, select the “Policy” link in the workflow state drop-down menu.
Select “Example policy” for “In this Folder” and “Below this Folder” and click “Save”.
Then, let’s add a Folder to see whether the new workflow policy is active. Go to the root of your site and select “Folder” from the “Add new item” drop-down list. Enter the id “myfolder”, the title “My folder” and the description “This is my folder”, and click on “Save”.
Now, when you access the “State” drop-down list, you will see that you have the possibility to “submit” the folder. The submit transition only exists in the “plone_workflow”, and is absent from the “folder_workflow”, which demonstrates that the workflow policy we have chosen is used for the “Folder” content type.
Let’s go one step further and add a new folder inside of “My folder”. After having added the new folder, you should also find the “Submit” transition available.
Now it would be interesting to change the workflow policy setting in the Plone site. Let’s first change the workflow policy for “Below this Folder” to “Default Policy”. You will find that the second folder does not more have the “submit” transition.
You can add an additional workflow policy in the first folder, which assigns the “My policy” for “In this Folder”, so the second folder will once again have the “submit” transition.
Additional tools
The Placeful Workflow tool (portal_placeful_workflow) is installed by the installer. It provides a few configuration options so that you use to create you workflow policies through the ZMI.
1.4.1 (2009-01-17)
Declare package dependencies and fixed deprecation warnings for use of Globals. [hannosch]
Define wtool inside the prefs_workflow_policy_mapping template. [hannosch]
Copied safeEditProperty from CMFPlone.migration_util to avoid a dependency. [hannosch]
1.4.0 (2008-11-05)
Port evolutions from the 1.3 maintenance branch (old style product). [encolpe]
Fixed bad version in metadata.xml (again) [encolpe]
Removed Favorite content type. [hannosch]
Fixed “ValueError: ‘acquisition’ is not a workflow ID” in prefs_workflow_policy_mapping. Fix prepared by jhackel. Fixes http://dev.plone.org/plone/ticket/8101 [maurits]
1.3.2 (2008-06-30)
Fixed bad metadata.xml. [encolpe]
Fixed incorrect variable name in exception message. [davisagli]
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Hashes for Products.CMFPlacefulWorkflow-1.4.1.tar.gz
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 | 3dfc97b173ff41e32705bd6b8293c3920f457d6a1fefc6fea63755ce6149a4f4 |
|
| MD5 | 7ef77f1631c25025980d5a60f60100ae |
|
| BLAKE2b-256 | 466a382b0545078e779864e9983889e938f135fa7dc819f5ab345951eb2073c2 |
