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

Unpublish and Delete Trigger

Often, within the context of a workflow process, there is a need to un-publish an asset before removing it from the system.

The DeleteAndUnpublish trigger can be used in place of the previous Delete trigger. When the asset in the workflow is not a publishable asset (template, symlink, stylesheet, block, reference), this new trigger performs a standard delete. However, when the asset is a "publishable" asset (file, page, folder) and has publishable destinations, the trigger attempts to un-publish the asset (and all child assets if it's a folder) from all destinations prior to removing it from the system.

Implementation

Declaration

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

Usage

<trigger name="DeleteAndUnpublish"/>

Parameters

None 

The following is the default Delete workflow distributed with the software with the DeleteAndUnpublish trigger used in place of the Delete trigger.

<system-workflow-definition initial-step="initialize" name="1 Step - Delete and Unpublish"> <!-- triggers that will be available to actions in the workflow --> <triggers> <trigger class="com.cms.workflow.function.EmailProvider" name="email"/> <trigger class="com.cms.workflow.function.Publisher" name="publish"/> <trigger class="com.cms.workflow.function.DeleteAndUnpublish" name="DeleteAndUnpublish"/> </triggers> <!-- steps that should happen in order --> <steps> <step identifier="initialize" label="Initialization" type="system"> <actions> <action identifier="initialize" move="forward" type="auto"> <trigger name="email"/> </action> </actions> </step> <step default-who="admin" identifier="final-review" label="Final Review (user)" restrict-to-type="role" restrict-to-value="Publisher" type="transition"> <actions> <action identifier="reject-to-edit" label="Cancel" next-id="canceled"> <trigger name="email"/> </action> <action identifier="approve" label="Approve" move="forward"> <trigger name="email"/> </action> </actions> </step> <step identifier="finalize-delete" label="Deleting" type="system"> <actions> <action identifier="finalize" move="forward" type="auto"> <trigger name="DeleteAndUnpublish"/> <trigger name="email"/> </action> </actions> </step> <step identifier="deleted" label="Deleted" type="system"> </step> </steps> <!-- non ordered steps --> <non-ordered-steps> <step identifier="canceled" label="Canceled" type="system"> </step> </non-ordered-steps> </system-workflow-definition>

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.