Page Navigation

• 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 Trigger
• 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

Most Read

• Web Services
• Code Sections
• Available Workflow Triggers
• Cascade Server CMS Primer
• Cascade Server CMS Primer Advanced
• Available System Tags
• System View Tags
• Available Plug-ins
• Authentication
• Data Definition Schema Reference

• Cascade Server 7.0 Beta 2 Release Notes
• Cascade Server 6.10.9 Release Notes
• Cascade Server 6.10.8 Release Notes
• Cascade Server 7.0 Beta Release Notes
• Cascade Server 6.10.7 Release Notes
• Cascade Server 6.10.6 Release Notes
• Cascade Server 6.10.5 Release Notes
• Cascade Server 6.10.4 Release Notes
• Cascade Server 6.10.3 Release Notes
• Cascade Server 6.10.2 Release Notes

Publish Parent Folder Trigger

The Publish Parent Folder Trigger publishes the parent folder of the asset in workflow.

Implementation

Declaration

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

Usage

<trigger name="PublishParentFolderTrigger"> <parameter> <name>destination</name> <value>/dest</value> </parameter> </trigger>

Parameters

Destination Parameter

The destination parameter is used to determine which destination the parent folder should publish to.  If more than one destination is required, these can be delimited by commas (",") within the same parameter. 

<parameter> <name>destination</name> <value>/dest</value> </parameter>

Authorizing-Type Parameter

The authorizing-type parameter is set when calling the trigger on an action. The authorizing-type parameter is used in any trigger that executes to a publish and is used to specify which user is "authorizing" the publish in this step. This will affect permissions/roles checks performed during publish and also to whom the publish report is delivered to. The "system" user is basically a way to bypass any permissions/roles checks but results in the publish report not being sent to anyone.

Authorizing-type can take a value of "current-step-owner," "system," or "user."

• current-step-owner - the user assigned to the step that calls the trigger
• system - the reserved "system" user
• user - a specified user

Authorizing-User Parameter

This parameter is used if 'user' is selected as the authorizing-type (in the parameter above). This parameter value can be any valid user name.

**Note - Authorizing-user will only be used if the authorizing-type parameter is set to the value of "user," rather than "current-step-owner," or "system."

If you were to use both the "authorizing-type" and "authorizing-user" parameters, your xml would look like this:

<trigger name="publish"> <parameter> <name>authorizing-type</name> <value>user</value> </parameter> <parameter> <name>authorizing-user</name> <value>johndoe</value> </parameter> </trigger>