NovoRoi Systems DokuWiki

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 syntax is:

NOVO.E.T filename UPDATE/DELETE ENABLE/DISABLE

• Filename is the file to be acted upon.

• 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

• 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

1. request the write of data to a file
2. execute the NovoMotion trigger
3. execute the Manage 2000 trigger
4. write the base file record to disk.

If the AFTER keyword is used the order of the triggers is reversed. The order then becomes

1. request the write of data to a file
2. execute the Manage 2000 trigger
3. execute the NovoMotion trigger
4. write the base file record to disk.

THIS IS USEFUL IF THE MANAGE 2000 TRIGGER IS CHANGING DATA ON THE BASE FILE THAT SHOULD BE RESPECTED BY THE NOVOMOTION TRIGGER.

Here is an example where the update trigger was enabled on the PT file:

:NOVO.E.T PT UPDATE ENABLE 
            
  Verify current trigger status...          
  Create Update Trigger...                  
  :LIST.TRIGGER PT                          
  BEFORE UPDATE TRIGGER: NOVO.UPDATE.TRIGGER
 BEFORE DELETE TRIGGER: not defined

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:

: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 you checked the trigger, here is what one would see:

:LIST.TRIGGER WC                                                      
  BEFORE UPDATE TRIGGER: GLOBAL.UPDATE.TRIGGER                          
 BEFORE DELETE TRIGGER: GLOBAL.DELETE.TRIGGER 

Now - if one enabled the trigger and accepted 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... 

And again - here is what one would see:

: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 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.

Here is an example using the AFTER keyword:

:NOVO.E.T WC ENABLE UPDATE DELETE AFTER
                                     
  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...

And again - here is what one would see:

:LIST.TRIGGER WC                                                      
  BEFORE UPDATE TRIGGER: NOVO.UPDATE.TRIGGER.AFT                            
 BEFORE DELETE TRIGGER: NOVO.DELETE.TRIGGER.AFT 

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

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.