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