User Tools
novo_motion_trigger_generator
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
novo_motion_trigger_generator [2018/11/07 18:02] novowiki /* NovoMotion Trigger Generator */ |
novo_motion_trigger_generator [2021/02/05 21:23] (current) dlm |
||
|---|---|---|---|
| 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. | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | It' | + | |
| Line 23: | Line 18: | ||
| - | * Filename is the file to be acted upon. | + | |
| - | * Either UPDATE or DELETE can be specified - both can be specified if needed | + | * Either |
| - | Example: NOVO.E.T IM UPDATE DELETE ENABLE | + | * Either **ENABLE** or **DISABLE** can be executed. |
| + | **Example: | ||
| - | * 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 | ||
| - | + | | |
| - | | + | - Execute |
| - | - execute | + | - Execute |
| - | - execute | + | - 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 | + | - Request |
| - | - execute | + | - Execute |
| - | - execute | + | - Execute |
| - | - 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. | + | 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. |
| 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 | + | Here is what the user will see when enabling |
| Line 107: | Line 101: | ||
| - | And again - here is what one would see: | + | Here are the results: |
| 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 |
| + | \\ | ||
| + | [[main_page|NovoMotion Outbound Menu]] | ||
novo_motion_trigger_generator.1541613745.txt.gz · Last modified: 2018/11/07 18:02 by novowiki
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
