Vincenzo Di Somma   Why Should You Learn More About Workflow In Plone
Upcoming SlideShare
Loading in...5
×
 

Vincenzo Di Somma Why Should You Learn More About Workflow In Plone

on

  • 3,007 views

As many Plone users already know, one of the most useful features that comes out of the box with Plone is the workflow of the contents. Plone comes not just with predifined workflow definitions but ...

As many Plone users already know, one of the most useful features that comes out of the box with Plone is the workflow of the contents. Plone comes not just with predifined workflow definitions but with a very powerful workflow engine which let you customize the life cycle of your content in the way you like more. You can manage security, task assignment and publishing state of your content, you can support the work of your editors and improve their work experience. Althoug it is a simple tool many Plone users still think about portal_workflow as a very obscure object. This session will try to explain many common and creative uses of the workflow functionalities in the newest releases of Plone, with lessons learned, common use cases and practical examples.

Statistics

Views

Total Views
3,007
Views on SlideShare
3,002
Embed Views
5

Actions

Likes
0
Downloads
55
Comments
0

1 Embed 5

http://www.slideshare.net 5

Accessibility

Categories

Upload Details

Uploaded via as OpenOffice

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Vincenzo Di Somma   Why Should You Learn More About Workflow In Plone Vincenzo Di Somma Why Should You Learn More About Workflow In Plone Presentation Transcript

    • Why you should learn more about workflow in Plone
      • Workflow from the beginning...
      • Vincenzo Di Somma
      • [email_address]
    • Life cycle of a content
      • The life cycle of a content involves two separate aspects:
      • Security
      • Task generation
    • Life cycle in a CMS
      • In a CMS environment the life cycle is usually managed using workflow tools
      • Plone uses CMF tools (DCWorkflow, CMFCore/WorkflowTool)
    • Workflow in Plone
      • By default the workflow in Plone is used to manage the publication process of a content.
      • It has more to do with permissions than tasks.
    • Hands on (1)
      • States
      • Transitions
      • The workflow process definition can be seen as an cyclic oriented graph, where states are nodes and transitions are arches.
    • Hands on (2)
      • Variables
      • Can be set automatically or manually on each state transitions and the different values will be preserved in the workflow history
    • Hands on (3)
      • Worklist
      • Collect reference to contents in a certain state for an easier task list generation
    • Hands on (4)
      • Permissions
      • Each wfpd can define which permission will be managed by the workflow
    • Hands on (5)
      • Groups
      • The association between Groups and roles can change depending on the state.
      • (I've never used it...but it doesn't mean it useless :)
    • What about the contents...?
      • How the wfpd are applied to content (types) ?
      • portal_workflow
      • cmfplacefulworkflow
    • Creating a custom WFPD
      • TTW
      • Python script
      • Generic Setup (xml)
    • Mixing workflows in a portal
      • Use case Smanettona
      • Default Plone publishing workflow for the corporate part of the site.
      • Restricted publishing workflow for the user home folders.
      • Restricted access to the howto section (hacks).
      • Very restricted publication workflow for the magazine area (Smantett'zina).
    • Smanett'zina
    • We can manage more that security
    • How to create a WFPD
      • TTW
      • Python Script
      • Generic Setup Profile (xml)
    • Common improvements
      • email alerts
      • explicit selection of actors (like rewievers) by group, sections, etc...
      • action accomplished by more than one actor in the same state (like multireview)
      • link transitions (content B is strictly related to content A, publishing the content A involve publishing also content B)
      • multisite life cycle (once a content is published in the portal A it is automatically available on porta B)
      • version management (when content is published, save the current version)
    • Thanks!
      • Questions...?