Page History

...

For examples of usage see the classe: editor_Workflow_Notification and editor_Workflow_Actions.

Field	Description / idea behind
id	DB auto incremented ID
workflow	defines to which workflow the action belongs. So only the actions for the workflow configured in the task are triggered. Currently the class inheritance hierarchy is reflected here. So for a Workflow class "foo" extending "default" all actions with both values are considered. This behavior will change in the future to enable the possibilty to disable extended default actions by child classes.
trigger	The named event trigger to react on. See list of available triggers below.
inStep	In step filter: the action is executed only if the tasks workflow is in the configured step. NULL means no filter.
byRole	By role filter: the action is executed only if the initiator of the trigger is in the configured role. NULL means no filter.
userState	userState filter: the action is executed only if the initiator of the trigger has the configured job status. NULL means no filter.
actionClass	the class where the to be called action is contained. Must inherit from "editor_Workflow_Actions_Abstract" class.
action	the action to be called
parameter	optional additional parameters, which are passed to the executed action. For example Mail notifications can be configured
position	Order of execution for entries with the same trigger configuration.

External Workflow Trigger

...

The value for the field trigger must contain the prefix: "handleDirect::" the rest of the string is the name of the trigger passed as POST parameter.

By default the notifyAllAssociatedUsers action is configured:

...

What	Value
Method	POST
URL	"/editor/task/ID/workflow" where the ID is the tasks DB id.
Parameter "trigger"	the trigger to be triggered, in the example above "notifyAllUsersAboutTaskAssociation"

...