Adding triggers to a process
Process Set processes are initiated based on the content being deployed, the channels involved in the deployment, and the trigger patterns associated with the content set. Trigger patterns fall into Name and URI categories. These identify what parts of the package resource are used to match against the pattern.
To add a trigger pattern to a process set
- On the Define tab, in the left menu, click Processes.
- Click the needed process set.
- In the Triggers section, click Add Trigger.
Enter the pattern.
The pattern must match the entire URI or TOC entry to relate content to the process set. You can use the wildcard character to generalize the content being handled. For example, **.war* would cause the handling of all content that ends in *.war, while a pattern of *war* would handle content with the text war anywhere in its evaluated name. When identifying patterns, ensure that they are not too generic. If a deployment includes files of the same type going to different destinations, then both the channel templates and the patterns need to distinguish the channels of one template from the other.
- Select the channel template to which this pattern applies.
Select the type of the trigger.
The following trigger types are supported:
Trigger type Description Filename The package reference with the file name matching the pattern triggers the process. Reference name The package reference with the reference name matching the pattern triggers the process. URI name The package reference with the URI matching the pattern triggers the process.
- Click Create.
You can also use the package reference name as a trigger type. You can provide any name to the package reference, and then trigger a process with the full reference name or its part by using a regex pattern. For more information, see discussion at BMC Communities.