Terminology Used in the MOCKUP --
Action -The bean identifier i.e.action_id of the actual action class as configured in the SPRING XML file like--
<bean id="{action.id}" scope="prototype"> <constructor-arg type="java.lang.String" value="{action.id}"/>
<property name="processingAction" ref="{action.api.id}"/>
<property name="requiresUI" value="{true/false}"/>
</bean>
Step-Container of Actions mapped to outcomes
Outcome-Numerical code which will map one step to the next step.
Process-Container of Steps in a certain order
For example- Analogous XML can be specified as---
<!--Standard workflow step--> <workflow start="traditional" id="default"> <step id="selectcollectionstep" role="submitter" userSelectionMethod="submit"> <outcomes> <step status="0">editstep</step> </outcomes> <actions> <action id="selectcollection"/> </actions> </step> </workflow>
The corresponding value of the fileds in the admin UI will be as follows--
Process-
Name-Traditional
Step1-
Name-SelectCollectionStep
UserSelectionID--SUBMIT
ROLE- SUBMITTER
Action1--Select Collection
Outcome--
0 --EditStep
1-- SelectCollectionStep(Incase there is some error)
This is just an initial overview of how one of those steps would be configured.I will add the whole analogy of the current submission-process to this page once I am done with admin UI and start coding the core ACTIONS.
