Mockup | ||||||||
---|---|---|---|---|---|---|---|---|
|
Terminology Used in the MOCKUP --
...
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> |
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
|
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.
1-- SelectCollectionStep(Incase there is some error)