Workflow Triggers

• Unpublish and Delete Trigger
• Preserve Current User Trigger
• Assign Step If User Trigger
• Assign To Group Owning Asset Trigger
• Assign To Workflow Owner Trigger
• Delete Trigger
• Publish Set
• Version Trigger
• Merge Trigger
• Publish Trigger
• Email Trigger
• New Workflow Trigger

NEWS & TIPS

• Site Access Keys
• Top: Alt+t
  Previous: Alt+,
  Next: Alt+.
  Up: Alt+;
  (Note: use Ctrl on the Mac)

Unpublish and Delete Trigger

Author: Bradley Wagner

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

Cascade Server 4.3 introduces a new workflow trigger called DeleteAndUnpublish located in the package "com.cms.workflow.function". It 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.

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="delete"/> </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="cancelled"> <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="delete"/> <trigger name="email"/> </action> </actions> </step> <step identifier="deleted" label="Deleted" type="system"> </step> </steps> <!-- non ordered steps --> <non-ordered-steps> <step identifier="cancelled" label="Cancelled" type="system"> </step> </non-ordered-steps> </system-workflow-definition>

Additional Notes

The only modification made to the workflow definition is the trigger assignment which assigns the trigger named "delete" to the DeleteAndUnpublish class instead of the standard Delete class.

Wiki | Edit