- Choose Tools > Administration > Triggers.
The Triggers window opens.
- Click Add.
The Add Trigger dialog opens.
- Enter a description.
- Select the file options. These options specify which files fire the trigger.
- Select Only in this branch: then choose a branch from the list to limit searches.
- Enter a repository name or click Browse to select a repository.
- Select Recursive to search all subrepositories in the specified repository.
- Enter the File(s) you want the trigger to fire for. You can enter a file name or wildcard characters.
- Select Use regular expression to perform a regex-style search instead of a wildcard search.
- Select Match case to enable case-sensitive searching.
- Select the Event options. These options specify when the trigger fires.
- Select before to add a pre-event trigger or after to add a post-event trigger.
- Select a file event from the list.
- To add a disabled trigger, clear Enabled.
- Select Disable trigger after it runs once if you only want the trigger to run one time. For example, you may want to send an email once after a particular user checks in a file.
- Select the Action options. These options specify what happens when the trigger fires.
- Select Run this script: and enter the full server script path. For security reasons, you cannot browse for a script.
- Select Send an email if you are adding an email trigger. Select users from the list of Surround SCM users. To add non-Surround users, click Add Email and enter an email address.
- Select Consolidate multiple file actions into one email to send one email for all files affected by the event. If this option is not selected, an email is sent for each file.
Note:
|
Security is not checked when email is sent. If users request to receive email when any
file is checked in to a mainline branch, they will receive an email if a file is checked in to a
repository that they are normally restricted from viewing. If your security restrictions are set
this way, it is recommended that the Surround SCM administrator manage all email triggers
and that general users do not have access to the My Email Notifications command.
|
- Click OK.
The trigger is added.