Starting Workflows

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:

Select Start Workflow from the toolbar. 

The Run Workflow dialog will open, allowing you to specify:

• Payload
  This can be a page, node, asset, amongst other resources.
• Title
  An optional title to help identify this instance.
• Comment
  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:

• Event Type
  The event type that will launch the workflow:
  • Created
  • Modified
  • Removed

• Notetype 
  The type of node that the workflow launcher applies to.
• Path
  The path that the workflow launcher applies to.
• Run Mode(s)
  The type of server that the workflow launcher applies to. Select Author, Publish, or Author & Publish.
• Conditions
  A list of conditions for node values that, when evaluated, determine whether the worklow is launched. For example, the following condition causes the workflow to launch when the node has a property name with the value User:
      name==User
• Features
  A list of features to be enabled. Select the required feature(s) using the drop down selector.
• Disabled Features
  A list of features to be disabled. Select the required feature(s) using the drop down selector.
• Workflow Model
  The workflow to launch when the Event Type occurs on the Nodetype and/or Path under the defined Condition.
• Description
  Your own text to describe and identify the launcher configuration.
• Activate
  Controls whether the workflow launcher is activated:
  • Select Enable to launch workflows when the configuration properties are satisfied.
  • Select Disable when the workflow should not execute (not even when the configuration properties are satisfied).
• Exclude List
  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:
  • property-name ignore any jcr event which triggered on the specified property name.
  • event-user-data:<someValue>  ignores any event that contains the <someValue> user-data set through the ObservationManager API.
  For example:
  jcr:lastModified,dc:modified,dc:format,jcr:lastModifiedBy,imageMap,event-user-data:changedByWorkflowProcess
  This feature can be used to ignore any changes triggered by another workflow process by adding the exclude item:
  event-user-data:changedByWorkflowProcess

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.

Open the Workflow console.

From the Models tab select the required workflow.

Click Start from the top navigation.

The Start Workflow dialog opens allowing you to enter the payload and an optional title and comment.

Specify the payload (includes pages, nodes, resources, and so on) to which the workflow is to be applied. You can use the drop down menu to browse the repository when selecting:

Click OK to start a workflow instance with the properties you configured. Now the workflow is running.

On the Workflow page, click the Launcher tab.

Click Add and configure the new workflow-to-node relationship as required:

• Event Type: The event type that will launch the workflow:
  • Created
  • Modified
  • Removed

• Nodetype: The type of node that the workflow launcher applies to.
• Path: The path that the workflow launcher applies to.
• Conditions: Conditions for node values that, when evaluated, determine whether the worklow is launched. For example, the following condition causes the workflow to launch when the node has a property name with the value User:

  name==User

• Workflow: The workflow to launch when the Event Type occurs on the Nodetype and/or Path under the defined Condition.
• Activate: Controls whether the workflow launcher is activated:
  • Select Enable to launch workflows when the configuration properties are satisfied.
  • Select Disable when the workflow should not execute when the configuration properties are satisfied.
• Exclude List
  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:
  • property-name ignore any jcr event which triggered on the specified property name.
  • event-user-data:<someValue>  ignores any event that contains the <someValue> user-data set through the ObservationManager API.
  For example:
  jcr:lastModified,dc:modified,dc:format,jcr:lastModifiedBy,imageMap,event-user-data:changedByWorkflowProcess
  This feature can be used to ignore any changes triggered by another workflow process by adding the exclude item:
  event-user-data:changedByWorkflowProcess
• Run Mode(s): The type of server that the workflow launcher applies to. Select Author, Publish, or Author&Publish.

Open the Tools console. (http://localhost:4502/miscadmin#/etc)

Navigate to Workflow, then Workflow Packages in the left pane.

Create a New Page...; assign a name of your choice and select the Workflow Package Template.

Open the new page.

For each resource add an instance of the Resource Definition component. Then either drag resources from the content finder, or edit the component to select a resource.