Workflow XML Reference - Triggering Events and Parameters
3 min
the following lists the types of events that can trigger actions, and the properties that are used in the xml workflow definition in most cases, the property is a child element of the triggering event element there are cases where the property requires its own block of child elements triggering event transition event properties (in required order) property requirement notes name required 24 character name maximum maximum 10 transitions per state must be connected to two states triggers optional the event's triggered actions each action is represented by its own \<trigger> child element block maximum 10 triggers per event fromstate required indicates the originating state tostate required indicates the destination state permissiongroups optional restricts the transition trigger to a specific set of users contains the following child element structure \<group> \<name> usergroup1name \</name> \</group> \<group> \<name> usergroup2name \</name> \</group> \<group> \<name> usergroupnname \</name> \</group> skippermissionchanges optional when included with a value of true , the aforementioned groups are not required to have the transition trigger the action triggering event propertychange event properties (in required order) property requirement notes name optional not required by the workflow definition, but useful for xml readability triggers required the event's triggered actions maximum 10 triggers per event propertyname required the name of a standard artifact property when this property changes, the action is triggered statecondition optional an optional condition placed on the above event parameter when the aforementioned artifact property changes, the action is triggered the artifact is in this state contains the following child element structure \<statecondition> \<state> statename \</state> \</statecondition> triggering event newartifact event properties (in required order) property requirement notes name optional not required by the workflow definition, but useful for xml readability triggers required the event's triggered actions maximum 10 triggers per event