The general workflow process definition language is quite complicated. For example, a programmer learning XPDL probably takes a week to basically master its general usage; in fact, this complexity should not be, the user needs a simple and The process definition language that is easy to understand. The process definition language of the AgileFlow is very simple, and its goal is to keep all of it within 1 hour.
The template for HPDL is as follows: XML Version = "1.0" encoding = "gb2312"?>
Processes represents multiple processes defined. Process Represents one of the processes. Activity indicates that the process / activity definition IDNAME represents the process / activity name CORRESPONDINGSUBPROCESSID indicates that the active ID of the activity corresponding to the activity ID, if not The corresponding subflow can not be configured by Jointype and the value AND or XOR, the default takes the value if the value is, indicating that the activity is completed, and this activity can begin if the value of XOR, indicating the activity of the activity There is any completion, this activity will begin nextActivity to represent the next activity of the activity such as active A-> B, then a NextActivity ID configured to be bdriveType can take the value of Auto / MAunal, default AUTO if AUTO, indicate When is completed, B will automatically start if the value manual, indicating that the user is completed, and the user has manually driven from A-> B, B.