NovoRoi Systems DokuWiki

User Tools

Site Tools

Trace:
novo_motion_trigger_generator

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
novo_motion_trigger_generator [2013/10/05 19:44] – /* NovoMotion Trigger Generator */ novowikinovo_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 +
- +
- +
- +
-Its sequesnce is:+
  
  
Line 23: Line 18:
  
  
-  * Filename is the file to be acted upon. +  * **Filename** is the file to be acted upon. Using **ALL** instead of a specific file name will enable/disable triggers on all filenames. 
  
  
-  * Either UPDATE or DELETE can be specified - both can be specified if needed+  * Either **UPDATE** or **DELETE** can be specified - both can be specified if needed.
  
  
-Example: NOVO.E.T IM UPDATE DELETE ENABLE+  * Either **ENABLE** or **DISABLE** can be executed. 
  
 +**Example:** NOVO.E.T IM UPDATE DELETE ENABLE
  
-  * Either ENABLE or DISABLE can be executed  
  
 +**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. 
  
-  * 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.  
  
 +If the **AFTER** keyword is used or if the NovoMotion version is 4.0 or greater, the order is as follows: 
  
-If the AFTER keyword is used or if the NovoMotion version is 4.0 or greater, the order is  
  
- +  - Request the write of data to a file  
-  - request the write of data to a file  +  - Execute the Manage 2000 trigger  
-  - execute the Manage 2000 trigger  +  - Execute the NovoMotion trigger 
-  - execute the NovoMotion trigger +  - Write the base file record to disk.  
-  - write the base file record to disk.  +
  
  
Line 50: Line 44:
  
  
-Prior to NovoMotion version 4.0 and with no AFTER keyword, the order is +Prior to NovoMotion version 4.0 and with no AFTER keyword, the order is as follows: 
  
  
-  - request the write of data to a file  +  - Request the write of data to a file  
-  - execute the NovoMotion trigger  +  - Execute the NovoMotion trigger  
-  - execute the Manage 2000 trigger  +  - Execute the Manage 2000 trigger  
-  - write the base file record to disk.  +  - Write the base file record to disk.  
    
    
Line 71: Line 65:
  
  
-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 one would see:+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:
  
  
Line 85: Line 79:
  
  
-If you checked the trigger, here is what one would see:+If the user then checked the trigger, here is the expected result: 
  
  
Line 93: Line 87:
  
  
-Now - if one enabled the trigger and accepted the overwrite:+Here is what the user will see when enabling the trigger and accepting the overwrite:
  
  
Line 107: Line 101:
  
  
-And again - here is what one would see:+Here are the results:
  
  
Line 115: Line 109:
  
  
-If the user DOES enable the NovoMotion trigger and an existing trigger is there, the NovoMotion trigger will execute the existing trigger code after it executes itself.   If the user's previous trigger is changing pertinent information in the file, it may be useful to execute the NovoMotion trigger after the existing trigger.  In that case the AFTER keyword is used to allow the existing trigger to call the NovoMotion 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. 
  
    
Line 125: Line 119:
  
  
-**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. +**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.
  
  
 +\\
 +[[main_page|NovoMotion Outbound Menu]]
  
novo_motion_trigger_generator.1381016661.txt.gz · Last modified: 2013/10/05 19:44 (external edit)