Differences

This shows you the differences between two versions of the page.

--- novo_motion_trigger_generator [2011/03/21 20:12] – novowiki
+++ novo_motion_trigger_generator [Unknown date] (current) – external edit (Unknown date) 127.0.0.1
@@ Line 1: / Line 1: @@
-{{file_jo_novo_logo_verbage3.gif}}
+[[main_page|NovoMotion Outbound Menu]]
+====== NovoMotion Trigger Generator ======
+The NovoMotion deployment package includes a process to enable and disable triggers. This process is executed in the U2 environment and is called NOVO.E.T
-===== **NovoMotion Trigger Generator** =====
+Its sequence is as follows:
-The NovoMotion deployment package includes a process to enable and disable triggers.  This process is executed in the U2 environment and is called NOVO.E.T
+NOVO.E.T filename or ALL;   UPDATE or DELETE; and  ENABLE or DISABLE
-Its syntax is:
+  * **Filename** is the file to be acted upon. Using **ALL** instead of a specific file name will enable/disable triggers on all filenames.
-NOVO.E.T filename UPDATE/DELETE ENABLE/DISABLE
+  * Either **UPDATE** or **DELETE** can be specified - both can be specified if needed.
+  * Either **ENABLE** or **DISABLE** can be executed.
-  * Filename is the file to be acted upon.
+**Example:** NOVO.E.T IM UPDATE DELETE ENABLE
-  * Either UPDATE or DELETE can be specified - both can be specified if needed
+**Please Note:** Versions of NovoMotion before 4.0 allow the additional keyword AFTER to be used to change the execution order of the existing trigger in conjunction with the new NovoMotion trigger. At release 4.0 and beyond, the AFTER keyword is the default syntax and is no longer allowed.
-Example: NOVO.E.T IM UPDATE DELETE ENABLE
+If the **AFTER** keyword is used or if the NovoMotion version is 4.0 or greater, the order is as follows:
-  * Either ENABLE or DISABLE can be executed
+  - Request the write of data to a file
+  - Execute the Manage 2000 trigger
+  - Execute the NovoMotion trigger
+  - Write the base file record to disk.
-  * The additional keyword AFTER can be used to change the execution order of the existing trigger in conjunction with the new NovoMotion trigger. The default ENABLE command will execute the NovoMotion trigger and then check for the existence of a Manage 2000 trigger.   Specifically the order of events are
+THIS IS USEFUL IF THE MANAGE 2000 TRIGGER IS CHANGING DATA ON THE BASE FILE THAT SHOULD BE RESPECTED BY THE NOVOMOTION TRIGGER.
-  - request the write of data to a file
+Prior to NovoMotion version 4.0 and with no AFTER keyword, the order is as follows:
-  - execute the NovoMotion trigger
-  - execute the Manage 2000 trigger
-  - write the base file record to disk.
+  - Request the write of data to a file
+  - Execute the NovoMotion trigger
+  - Execute the Manage 2000 trigger
+  - Write the base file record to disk.
-If the AFTER keyword is used the order of the triggers is reversed.  The order then becomes
+Here is an example where the update trigger was enabled on the PT file:
-  - request the write of data to a file
+  :NOVO.E.T PT UPDATE ENABLE
-  - execute the Manage 2000 trigger
-  - execute the NovoMotion trigger
+    Verify current trigger status...
-  - write the base file record to disk.
+    Create Update Trigger...
+    :LIST.TRIGGER PT
+    BEFORE UPDATE TRIGGER: NOVO.UPDATE.TRIGGER
+   BEFORE DELETE TRIGGER: not defined
-THIS IS USEFUL IF THE MANAGE 2000 TRIGGER IS CHANGING DATA ON THE BASE FILE THAT SHOULD BE RESPECTED BY THE NOVOMOTION TRIGGER.
+If a trigger already exists on the file being enabled, the user is asked to specify if the new trigger should replace the existing trigger.  Users can choose to enable at their discretion.  Here is what the user will see:
+  :NOVO.E.T WC ENABLE UPDATE DELETE
+    Verify current trigger status...
+    This file already has an UPDATE trigger defined: GLOBAL.UPDATE.TRIGGER
+    Replace it? ?N
+    ... UPDATE trigger will not be replaced.
+    This file already has an DELETE trigger defined: GLOBAL.DELETE.TRIGGER
+    Replace it? ?N
+   ... DELETE trigger will not be replaced.
+If the user then checked the trigger, here is the expected result:
+  :LIST.TRIGGER WC
+    BEFORE UPDATE TRIGGER: GLOBAL.UPDATE.TRIGGER
+   BEFORE DELETE TRIGGER: GLOBAL.DELETE.TRIGGER
+Here is what the user will see when enabling the trigger and accepting the overwrite:
+  :NOVO.E.T WC ENABLE UPDATE DELETE
+    Verify current trigger status...
+    This file already has an UPDATE trigger defined: GLOBAL.UPDATE.TRIGGER
+    Replace it? ?Y
+    This file already has an DELETE trigger defined: GLOBAL.DELETE.TRIGGER
+    Replace it? ?Y
+    Create Update Trigger...
+   Create Delete Trigger...
+Here are the results:
+  :LIST.TRIGGER WC
+    BEFORE UPDATE TRIGGER: NOVO.UPDATE.TRIGGER
+   BEFORE DELETE TRIGGER: NOVO.DELETE.TRIGGER
+If the user DOES enable the NovoMotion trigger and an existing trigger is there, the NovoMotion trigger will execute the existing trigger code before it executes itself.
+**NOTE:**  There is also a global RECOMPILE keyword that is only used when new versions of the software are installed.  Its syntax is:
+  :NOVO.E.T RECOMPILE
-Here is an example where the update trigger was enabled on the PT file:
+**Additional Usage Notes:** If a U2 file is about to be purged yet the user wishes to retain the data in the related SQL table - even though a U2 DELETE trigger exists - the user would DISABLE the DELETE trigger for the file, purge the file, and then ENABLE the trigger.
- :NOVO.E.T PT UPDATE ENABLE
+\\
+[[main_page|NovoMotion Outbound Menu]]
-  Verify current trigger status...
-  Create Update Trigger...
-  :LIST.TRIGGER PT
-  BEFORE UPDATE TRIGGER: NOVO.UPDATE.TRIGGER
- BEFORE DELETE TRIGGER: not defined