Changes between Version 6 and Version 7 of WorkFlow


Ignore:
Timestamp:
01/28/11 07:59:52 (4 years ago)
Author:
anna
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WorkFlow

    v6 v7  
    1 == Workflow, Roles and Permissions == 
    2  
    3 Plone ships with a sophisticated work flow and permissions system. A work flow is a series of steps that are followed in order to complete a task. In the case of Plumi most often it's the process of publishing a video. Permissions are about what powers a user with a given role has on the site to add or change content, or change the way the site works. 
    4  
    5 === Workflows === 
    6  
    7 Plone allows you to set quite extensive work flows and levels of permissions. The settings for Plumi are explained below. They are configured inside [https://svn.plone.org/svn/collective/plumi.skin/ Plumi Skin]. 
    8  
    9 The video publishing work flow for Plumi is: 
    10  * The site member goes through 3 step publishing form and hits save on final step 
    11  * The video item goes into the "pending" state awaiting approval. The member cannot edit the video in "pending" unless they select "retract" in the top right where it says "state". After retracting they must then re-submit the video for approval by selecting "submit". 
    12    * '''note''': Items in the state "public draft" are just that, public, they do not however appear in video listings or in the members personal vodcast. Items in "pending" are also viewable publicly. 
    13  * An email is sent to site managers informing them a video is awaiting approval.  
    14  * The manager can either accept the video by changing the state to "published" or "reject" or "retract" it. 
    15  * A retracted or rejected video goes into public draft. An manager can also choose to make the item private or delete it. 
    16  * If the video is approved the contributing member receives an email notification letting them know. 
    17  
    18 For more information on workflows see http://plone.org/documentation/tutorial/creating-workflows-in-plone/ 
    19  
    20 === Roles and Permissions === 
    21 "Permissions are low-level things - they specify that a user can do exactly A, but not B in a given context. Permissions are used as guards on access to methods, scripts, page templates, workflow transitions and sometimes individual components on a page." [http://plone.org/documentation/tutorial/understanding-permissions/permissions-and-roles Plone: Understanding Permissions] 
    22  
    23 Plumi sets four default levels of users: Member, Reviewer, Manager and Editor. It is however possible to add many more. You can set what these users can and cannot do and add new roles in the Zope Management Interface (where exactly?) or through the back end. 
    24  
    25 By default Reviewers and Managers can approve videos for inclusion in listings and vodcasts. Reviewers have no ability to change the configuration of the site and can only approve or reject content. 
    26  
    27 More on permissions and roles: http://plone.org/documentation/tutorial/understanding-permissions/ 
    28  
    29  
     1This page is deprecated. Please see the Plumi Manual - http://en.flossmanuals.net/Plumi/