Process Definition Language of agileflow

Generally, the workflow definition language is quite complex. For example, it takes about one week for a programmer to learn xpdl.
Master its general usage; in fact, for users, this complexity is not appropriate, users need a simple and easy
Understand the process definition language.
The Process Definition Language hpdl used by agileflow is very simple. Its goal is to allow you to master all of it within one hour.

The hpdl template is as follows:
<? XML version = "1.0" encoding = "gb2312"?>
<Processes>
<Process id = "" name = "">
<Activity id = "" name = "" correspondingsubprocessid = "" jointype = "And/XOR">
<Nextactivity id = "" drivetype = "manual/auto"/>
</Activity>
</Process>
</Processes>

Processes indicates multiple processes defined.
Process indicates a process.
Activity indicates an activity in the process.
Id indicates the workflow/activity definition ID.
Name indicates the process/activity name.
Correspondingsubprocessid indicates the definition ID of the sub-flow corresponding to the activity. If the sub-flow is not configured
Jointype can be set to and or XOR. The default value is and.
If the value is "and", it indicates that the activity can start only after the previous activities of the activity are completed.
If the value is XOR, it indicates that any previous activity of the activity is completed and the activity starts.
Nextactivity indicates the next activity of an activity, for example, activity a-> B. The ID of nextactivity of A is set to B.
Drivetype can be set to auto/maunal. The default value is auto.
If the value is auto, it means that when a is completed, B will start automatically
If the value is manual, it indicates that when a is complete, the manual drive must start from a --> B, B.