Available Workflow Triggers

• Publish Trigger
• Preserve Current User Trigger
• Assign To Group Owning Asset Trigger
• Assign Step If User Trigger
• Assign to Specified Group Trigger
• Assign To Workflow Owner Trigger
• Email Trigger
• Version Trigger
• Merge Trigger
• Publish Set
• Delete Trigger
• Unpublish and Delete Trigger
• Create New Workflow Trigger
• Publish Parent Folder Trigger
• Delete Parent Trigger
• Copy Folder Trigger
• Publish Containing Publish Set Trigger

• Cascade Server 5.7.2 Release Notes
• 2008 User's Conference Presentation Files
• Cascade Server 5.7.1 Release Notes
• Cascade Server 5.7 Release Notes
• Cascade Server 5.5.2 Release Notes
• Cascade Server 5.5.1 Release Notes
• Cascade Server 5.5 Release Notes
• New Asset Factory and Workflow Trigger Plugins
• Cascade Server 5.2.4 Release Notes

Email Trigger

Including this trigger will provide an email notification for the step immediately following.  If no parameters are added, the following behavior will result:

• if the step immediately following this trigger is a transition step, the trigger will send an email to the owner (either a single user or a group of users) of that transition step.
• if there is not a transition step following the trigger execution step, the trigger will notify the owner of the workflow, because a system step or absence of a next step will not provide email information to the trigger.

Implementation

Declaration

<trigger class="com.cms.workflow.function.EmailProvider" name="EmailProvider"/>

Usage

<trigger name="EmailProvider"> <parameter> <name>mode</name> <value>notify</value> </parameter> <parameter> <name>recipients-email</name> <value>a@b.com,b@c.com, d@e.com, f@g.com</value> </parameter> </trigger>

Parameters (Optional)

Although not required, four optional parameters may be used, which will change the default behavior described above:

Email Address Parameter

This is an optional parameter inside the email trigger that allows you to specify non-system email addresses to be notified.

To specify who should receive notifications, the following parameter should be added to the email trigger with the list of emails comma delimited:

<parameter> <name>recipients-email</name> <value>a@b.com,b@c.com, d@e.com, f@g.com</value> </parameter>

Inside the email trigger it will look like this:

<trigger name="EmailProvider"> <parameter> <name>mode</name> <value>notify</value> </parameter> <parameter> <name>recipients-email</name> <value>a@b.com,b@c.com, d@e.com, f@g.com</value> </parameter> </trigger>

Recipient Users Parameter

This is an optional parameter inside the email trigger that allows you to specify system users to be notified.

To specify who should receive notifications, the following parameter should be added to the email trigger with the list of emails comma delimited:

<parameter> <name>recipient-users</name> <value>user1,user2,user3</value> </parameter>

Recipient Groups Parameter

This is an optional parameter inside the email trigger that allows you to specify system groups to be notified.

To specify who should receive notifications, the following parameter should be added to the email trigger with the list of emails comma delimited:

<parameter> <name>recipient-groups</name> <value>group1,group2,group3</value> </parameter>

Mode Parameter

This parameter determines when a notification should be sent. If the value is "notify", then the user will receive a notification when a workflow has been assigned to him/her. If the value is "completed", then the user will receive a notification when the workflow has been completed. If the mode is not specified, the default is "notify".

<parameter> <name>mode</name> <value>completed</value> </parameter>

Adding a Workflow Trigger

The Cascade Server workflow builder utilizes centrally managed triggers.  For a trigger to be available in a workflow created by the Workflow Builder, the trigger must first be defined and assigned a name in the system-wide trigger base.  Defining triggers in this way allows the Java files that contain each trigger’s functionality to be referenced later in the workflow definition.

If a new custom trigger has been written or Cascade Server has been upgraded without including the default database, the new triggers will need to be added before they become available in the Workflow Builder.

To add a workflow trigger:

1. In the Administration area, select ‘Workflow Definitions’.
   
2. Click ‘Manage Workflow Triggers’.
   
3. All currently available triggers in the default database are shown, along with the ‘Add a Trigger’ field.
   
4. Type in the name of the new trigger and click ‘Submit’.
   
5. The new trigger will now appear on the list of available triggers and will be available for use within the Workflow Builder.

Adding a trigger using this interface ensures that the triggers will be defined in all workflows created using the Workflow Builder.  For workflows created without the Workflow Builder, triggers must be defined individually for each workflow.