| Script Name | Status* | |
| Jobs.pl | 
| Example trigger to enforce a rule "submissions must be associated with a job.". |
| Jobs.sh |
| Similar to above, but contributed by Wes Peters and written in Unix "shell". Takes a different approach to the problem, running "p4 fixes" to determine whether you're fixing something with this submission. |
| CheckC.pl | 
|
A script to notice when you're creating new files (or integrating to a new
branch) and the directory name you're writing the [new] file to isn't the
same case as an existing directory name.
(For example, if "//depot/x/y/z.c" exists, this won't allow you to create a file named "//depot/X/Y/one.c".) |
| Pairs.pl |
| Example trigger to enforce a rule "files of suffix .x/.y need to be checked in as pairs". |
| Binary.pl |
| Example trigger to enforce a rule "submissions of .gif must binary files and .sh files should be text and...." |
| simple.cmd | 
| Classroom example of writing a trigger using the Windows/NT command shell, a.k.a. "a .cmd script". (It checks that "Bug:" is included in the change description.) Doesn't do a lot, but gets the idea across. |
*How to interpret the "Status" field:
- a smiley face means "it's probably simple enough to use without any worries that it'll corrupt or slow down anything" ;
- a scared face means "you probably want to read the comments at the top of the script - this might need localization/tailoring or might have performance implications you want to investigate before deploying on your production Perforce server" ;
- and "under construction" means just that - you can look, you can make copies, but it's getting reworked at the moment.