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 Containing Publish Set Trigger

This trigger is used to publish out publish sets that the asset in workflow is a member of. The trigger can be used in two ways. First, it can publish out all publish sets in a specified container that contains the asset attached to the workflow. Alternatively, it can be used to publish out one particular publish set if it contains the asset in workflow. This trigger will look for the publish set container or publish set by path inside of the same Site to which the asset in the workflow belongs.

Implementation

Declaration

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

Usage

Parameters

Four parameters may be used to specify which publish set containers get published:

Publish Set Container Path Parameter

This parameter is used to identify a publish set container by its path. Note: the name parameter must be the string 'container-path.'
<parameter> <name>container-path</name> <value>/site</value> </parameter>

Publish Set Container Id Parameter

This parameter is used to identify a publish set container by its id. Note: the name parameter must be the string 'container-id'.

<parameter> <name>container-id</name> <value> c3e953120a00018200437b9a9e69f612 </value> </parameter>

Publish Set Path Parameter

This parameter is used to identify a specific publish set by its path. Note: the name parameter must be the string 'path'.

<parameter> <name>path</name> <value>/site/publishset</value> </parameter>

Publish Set Id Parameter

This parameter is used to identify a specific publish set by its id. Note: the name parameter must be the string 'id'.

<parameter> <name>id</name< <value>e7b599550a000182012f15b045877174</value> </parameter>

Authorizing-Type Parameter

The authorizing-type parameter is set when calling the trigger on an action. 

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>