| Mockup | |||||||||
|---|---|---|---|---|---|---|---|---|---|
|
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--
| Code Block |
|---|
<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---
| Code Block |
|---|
<!--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>
|
In the above screen the process belongs to the level where the user is currently present.So,it can be community-specific or collection-specific or whole intance-specific.
The order of steps to be taken will be determined in the order in which they are created in the above screen.
