Re: OSW Parallel steps

James,

    As I understand OSWorkflow I would describe the workflow you propoused
this way:

    Step 0. Initialize Workflow
        Action 0. Initialize -> Go to Step 1 / docNumber = 0;

    Step 1. Initialize review board
        Action 1. Add reviewer - > Got to Step 1 / ++docNumber;
        Action 2. Finish review board initialization -> Go to Step 2

    Step 2. Review Document
        Action 3. Accept Document  -> Go to Step 2 / -- docNumber;
        Action 4. Reject Document  -> Go to Step 3 / -- docNumber;
        Action 5. Finish Review [docNumber == 0] -> Go to Step 3

    Step 3. Review Finished

    Where docNumber is stored in the PropertySet, and maybe Action 5 can be
automatically triggered.

    We are using 2.5 from the CVS.

    You can extended AbstractWorkflow, actually we do. It isn't difficult
but the code is monolitic, so extending is a little bit ugly.

    +1 on replacing primitive types with objects, I mentioned this before in
the list.

    Hope this help.

Aníbal

----- Original Message -----
From: <[email protected]>
To: <    >
Sent: Wednesday, June 11, 2003 6:01 PM
Subject: [Opensymphony-developers] Parallel steps


> We have downlowed OSWorkflow 2.1.0, and have a question about how to run a
> particilar workflow.
>
> Workflow actors: chairman, reviewer
>
> Workflow process:
> 1. Initialize review board  (done by chairman)
>        - task is to create reviewer list, one entry per reviewer
> 2. Review document  (done by reviewer)
>      - This is a split workflow, one entry per reviewer in reviewer list
>     - Each reviewer has a due date associated with their task
>     -  Each individual reviewer either rejects or accepts the document
>    - The chairman can 'proxy-vote' for individual reviewers
> 3. Finish review (done by chairman)
>    - This is a join step, completed when all reviews are complete
>
> I see within OSWorkflow 2.1.0 that a split will work for distinctly-named
> steps.
>
> Some function-related questions...
> How can I do a split a using the same step, with a separate step instance
> per member of an input list?
> Do I have to extend AbstractWorkflow?  Has someone done this already?
> How would I set a due date for a step/owner combination?
>
> Some API-related questions...
> Is there an easy way to find the steps associated with a particular owner?
> Is there an easy way to find the available actions associated with a
> particular step and owner combination?
> Could we add an sub-interface to Workflow that returns objects instead of
> primitive ids?
>
>
>
>
> "NOTICE - This e-mail message may contain privileged, confidential, or
> proprietary information intended only for the use of the intended
> recipient.  If you are not the intended recipient of this e-mail, you are
> hereby notified that any use, dissemination, distribution or reproduction
> of this e-mail is prohibited.  If you have received this e-mail in error,
> please notify Bombardier Aerospace immediately and delete this e-mail and
> all attachments from your computer system.  Any views expressed in this
> e-mail are those of the individual sender and may not necessarily reflect
> the views of Bombardier Aerospace."
>
>
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by: eBay
> Great deals on office technology -- on eBay now! Click here:
> http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
> _______________________________________________
> Opensymphony-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/opensymphony-developers
>
>



-------------------------------------------------------
This SF.NET email is sponsored by: eBay
Great deals on office technology -- on eBay now! Click here:
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5