Publish Trigger
This trigger publishes the current asset in workflow, if it is able to be published, to all of its available destinations. Additionally, you can create custom workflows that publish content only to specified destinations by passing parameters to the trigger in the workflow definition.
When using the publish trigger, remember that the system differentiates between standard transition steps and system steps. System steps that call the publish trigger continue to publish out content as the implicit system user (which operates as an administrator-level user), whereas transition steps consider the role of the current user who has ownership of the step.
If a publish trigger is executed during a transition step, a user with an Approver role, for example, would not have sufficient privileges to publish out the content.
Implementation
Declaration
Usage
Parameters
Note that specifying these parameters is completely optional. Unless you specify, the system will publish to all applicable destinations. This is only for administrators wanting to publish to a subset of the applicable destinations for a given workflow definition.
Destination Parameter
You can specify multiple destinations by putting in multiple parameter nodes, each containing a name and value tag, such as:
Please note that the path to the destination is case sensitive.
Working-Copy-Publish Parameter
It is also possible to publish the working copy of a page in workflow for staging purposes. This can be accomplished by adding a working-copy-publish parameter to the invocation of the publish trigger in a workflow definition with a value of true. By default (without this parameter) only the non-working copy version of the asset in workflow is published.
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: