The procedure for disabling a trigger depends on how the trigger was created, as summarized in the following table:
Table 1: Procedures for disabling triggers Change Package-level integration. Using the mktrig command. The rmtrig command. Transaction-level integration (or “affectedFiles triggers”) Putting scripts in a “triggers” directory. Rename the script, or the entire directory..../storage/depots/depotname/triggersGlobal repository (site_slice) triggers:.../storage/site_slice/triggers Depot specific trigger: server_preop_trigGlobal repository site_slice trigger:NOTE: If you rename the script, you must modify the name of the script, not just the extension. For example, to disable server_admin_trig, it is NOT sufficient to rename the script from server_admin_trig.bat to server_admin_trig.BAK. You must modify the filesname itself, such as server_admin_trig_BAK.bat, otherwise AccuRev will return an error that the trigger server_admin_trig cannot be executed.
AccuRev, Inc. |
Phone: 781-861-8700 |
Fax: 781-861-8704 |
support@accurev.com |