Open topic with navigation
Perforcetriggers are user-written programs or scripts that are called by a
whenever certain operations (such as changelist submits, changes to
forms, attempts by users to log in or change passwords) are performed. If
the script returns a value of
0, the operation continues; if
the script returns any other value, the operation fails.
Triggers allow you to extend or customize Perforce functionality. Consider the following common uses:
file1is submitted in a changelist,
file2is also submitted.
p4 clientcommand, or to ensure that users always enter a meaningful workspace description.
To configure Perforce to work with external authentication mechanisms such as LDAP or Active Directory.
You might prefer to enable LDAP authentication by using an LDAP specification. For more information, see section Authentication options.
For simplicity’s sake, this guide refers to trigger scripts and programs as triggers.
If the API level is 79 or greater, canonical filetypes are now displayed by default for all commands that display filetypes. If the API level is 78 or lower, filetype aliases are displayed instead. If your script depends on the display of filetype aliases, you will need either to change the API level or to change your script.