Re: [Phpwebsite-developers] Workflow

[Matthew M. <ma...@tu...>]

Ok here is how it works.

There is a module called Version. It handles two main components: 1)
backing up old material, 2) controlling approval.

There are two types of rights in 1.0.0. A user can be restricted or
unrestricted. An unrestricted user can perform all the permissions
assigned to them without impediment. A restricted user's permissions
apply only to items assigned by an unrestricted user.

For example, I am unrestricted. I create a announcement about
phpwebsite. Steven is restricted. He has edit permissions. If I give him
permission to edit the announcement about phpwebsite, he may do so but
ONLY for that item.

If Steven makes an edit of my announcement, Version makes an unapproved
version of the original. Now when I go back in I can:
1) edit his unapproved changes and leave it unapproved,
2) edit (or not) his changes and approve the announcement,
3) decline his changes.

If approved, his version replaces the announcement. Any approved
announcements (including mine which would be pre-approved) are backed up
as versions. If I wish to restore to a previous version, I go to my
version list and pick the one I want to restore.

The above is already written. The next step is coding the Workflow
module. This module will allow you to create a group of individuals who
have 'steps' and will work with Version. As people work on an item, it
is passed to the next person in the chain for approval.
I will reveal more once I get into it.

As a heads up, I am going back to testing under Postgres as I have been
using MYSQL for a bit. Once I get that working (the code isn't lacking,
it's my understanding of postgres), I am returning to work on
Categories. Once finished, it will replace FatCat and I can start
writing the crutch files for it. We will be really close to backward
compatibility at that point.

Matt

On Sat, 2004-11-27 at 19:55, Shaun Murray wrote:
> On 27 Nov 2004, at 12:46, chris mcginlay wrote:
> 
> > Hello,
> >
> > I am interested to know what plans for improved workflow / 'approval' 
> > are in
> > the pipeline. Since I need these features I would be willing to write 
> > some of
> > the code. I had in mind a transaction database, or at least a 
> > transaction
> > table along with an edit-locking mechanism. Upon approval entries in 
> > the
> > transaction table would be commited to the database and the edit-lock
> > removed.
> >
> > What I don't know is if there are any plans already that I could 
> > discuss.
> 
> Matt's been sorting out Workflow and also revision control for v1.0 
> (the release formally known as v0.9.4). I don't know if it's in the 
> phpwebsite094 cvs folder already but Matt's your man to discuss it 
> with.
> 
> 
> Shaun
> aegis design - http://www.aegisdesign.co.uk
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now. 
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
-- 
Matthew McNaney
Internet Systems Architect
Electronic Student Services
Appalachian State University
Phone: 828-262-6493
http://phpwebsite.appstate.edu
http://ess.appstate.edu