When administering workflows you can start them using a variety of methods:
Other methods are also available to authors; for full details see:
You can start a workflow based on one of the models listed on the Workflow Models console. The only mandatory information is the payload, though a title and/or comment can be added as well.
The Workflow Launcher monitors changes in the content repository to launch workflows dependent on the location and resource type of the changed node.
Using the Launcher you can:
A launcher can be created for any node. However, changes to certain nodes do not launch workflows. Changes to nodes below the following paths do not cause workflows to launch:
Any workflow-inbox node located anywhere in the
/var/statistics/trackingdo cause workflows to launch.
Various definitions are included with the standard installation. These are used for digital asset management and social collaboration tasks:
Workflow packages are packages that can be passed to a workflow as payload for processing, allowing multiple resources to be processed.
A workflow package:
Navigate to the Models console using Tools, Workflow, then Models.
Select the workflow (according to the console view); you can also use Search (top left) if required:
The Transient indicator shows workflows for which the workflow history will not be persisted.
Select Start Workflow from the toolbar.
The Run Workflow dialog will open, allowing you to specify:
This can be a page, node, asset, package, amongst other resources.
An optional title to help identify this instance.
An optional comment to help indicate details of this instance.
Navigate to the Workflow Launchers console using Tools, Workflow, then Launchers.
Select Create, then Add Launcher to open the dialog:
The event type that will launch the workflow:
The type of node that the workflow launcher applies to.
The path that the workflow launcher applies to.
The type of server that the workflow launcher applies to. Select Author, Publish, or Author & Publish.
A list of conditions for node values that, when evaluated, determine whether the workflow is launched. For example, the following condition causes the workflow to launch when the node has a property name with the value User:
A list of features to be enabled. Select the required feature(s) using the drop down selector.
A list of features to be disabled. Select the required feature(s) using the drop down selector.
The workflow to launch when the Event Type occurs on the Nodetype and/or Path under the defined Condition.
Your own text to describe and identify the launcher configuration.
Controls whether the workflow launcher is activated:
This specifies any JCR events to exclude (i.e. ignore) when determining whether a workflow should be triggered.
This launcher property is a comma separated list of items: ``
jcrevent which triggered on the specified property name. ``
event-user-data:<*someValue*>ignores any event that contains the
user-dataset through the [
This feature can be used to ignore any changes triggered by another workflow process by adding the exclude item:
Select Create, to create the launcher and return to the console.
Once the appropriate event occurs the launcher will be triggered and the workflow started.
After you have created your launcher configuration you can use the same console to select the instance, then View Properties (and edit them) or Delete.