[JIRA-OS] Commented: (WF-207) Flawed logic in Actions definition of OSWorkflow

The following comment has been added to this issue:

     Author: Egor Kobylkin
    Created: Fri, 12 Sep 2003 6:48 AM
       Body:
OK, I have made actually more changes that that. We have already discussed it in the email correspondence.
I think you can close the issue now, Hani.
---------------------------------------------------------------------
View the issue:

  http://jira.opensymphony.com/secure/ViewIssue.jspa?key=WF-207


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: WF-207
    Summary: Flawed logic in Actions definition of OSWorkflow
       Type: Improvement

     Status: Assigned
   Priority: Minor

    Project: OSWorkflow
 Components: 
             Documentation
   Versions:
             2.5

   Assignee: Hani Suleiman
   Reporter: Egor Kobylkin

    Created: Thu, 4 Sep 2003 7:31 AM
    Updated: Wed, 10 Sep 2003 1:24 PM
Environment: wiki

Description:
EK(Egor Kobylkin comment):It really took me a long time to understand here what is what, it seems the explanation makes me run in circles:

http://wiki.opensymphony.com/space/OSWorkflow+Workflow+Concepts
Steps, Status, and Actions
...
For the workflow to progress, a transition must take place in the finite state machine that represents a workflow instance.
This behavior is possible via actions. Actions are nothing more than a list of all the possible transitions from one state (which is a step/status combination) to another state. 
[EK: So, I suppose, every Action is a list of transitions, in a nutshell.]
The transitions are decided by the end user, from a selection of all possible actions. 
[EK: Aha! A transition must be just an Action then. 
Circle is closed and I am no smarter than at the start of the paragraph.]
End of quotation

Here is my proposal for this paragraph: 

For the workflow to progress, a transition must take place in the finite state machine that represents a workflow instance.
Transition is a result of an action. Each step may have many actions connected to it. Which particular action will be launched is determined by the end user. Depending on the action accomplished, a certain transition takes place. Actions can be restricted to particular groups and users or current state of the workflow. Each action must have one unconditional result (default) and zero or more conditional results.



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.opensymphony.com/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf