novo_motion_trigger_generator
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| novo_motion_trigger_generator [2021/02/05 15:21] – dlm | novo_motion_trigger_generator [Unknown date] (current) – external edit (Unknown date) 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | [[main_page|NovoMotion Outbound Menu]] | ||
| ====== NovoMotion Trigger Generator ====== | ====== NovoMotion Trigger Generator ====== | ||
| Line 18: | Line 18: | ||
| - | * Filename is the file to be acted upon. Using ALL instead of a specific file name will enable/ | + | |
| - | * Either UPDATE or DELETE can be specified - both can be specified if needed. | + | * Either |
| - | * Either ENABLE or DISABLE can be executed. | + | * Either |
| - | Example: NOVO.E.T IM UPDATE DELETE ENABLE | + | **Example:** NOVO.E.T IM UPDATE DELETE ENABLE |
| - | * 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. | ||
| + | **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. | ||
| - | If the AFTER keyword is used or if the NovoMotion version is 4.0 or greater, the order is | + | |
| + | If the **AFTER** keyword is used or if the NovoMotion version is 4.0 or greater, the order is as follows: | ||
| Line 43: | 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: |
| Line 64: | 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 78: | 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 86: | Line 87: | ||
| - | Now - if one enabled | + | Here is what the user will see when enabling |
| Line 100: | Line 101: | ||
| - | And again - here is what one would see: | + | Here are the results: |
| Line 121: | Line 122: | ||
| + | \\ | ||
| + | [[main_page|NovoMotion Outbound Menu]] | ||
novo_motion_trigger_generator.1612556481.txt.gz · Last modified: 2021/02/05 15:21 (external edit)