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.3 Release Notes
• 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

Preserve Current User Trigger

This trigger acts as a solution for an issue that sometimes arises when you submit a workflow to a group instead of a user.

Typically, if you choose Assign to Me when receiving that group workflow step, the system will only temporarily give you ownership of the step. If you choose Edit, the system will resend ownership of the asset back to the group; that will allow it to be picked up by another user in the group who would then be routed to the edit screen.

This trigger is used to keep the user who originally clicked Assign to Me in memory for the duration of the workflow. This way when a user makes changes and submits the asset back to the original user, who then reviews it, the asset will not go back to the group but to the user (who selected Assign to Me) for publishing.

Implementation

Declaration

Please declare the trigger in the section using the following tag:

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

Usage

Please place the following trigger within your element in the step that is for the group action:

<trigger name="preserveCurrentUser"/>

For example, if you have a step assigned to a group and one of the options was to "Edit" as well as a separate option to "Approve", you would put the preserve current user trigger as a trigger for both steps, assuming you want the user preserved instead of the group assignment.

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.