novo_event.handler
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
novo_event.handler [2021/02/04 15:42] – dlm | novo_event.handler [2021/02/05 16:20] (current) – dlm | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | [[main_page|NovoMotion Outbound | ||
====== NOVO.EVENT.HANDLER ====== | ====== NOVO.EVENT.HANDLER ====== | ||
Line 5: | Line 5: | ||
- | This is a subroutine that is used by the processes to generate [[bci.action]] records. The subroutine may be invoked within custom processes - if desired. This would then replace the normal triggering process. | + | This is a subroutine that is used by the processes to generate [[bci.action|BCI.ACTION]] records. The subroutine may be invoked within custom processes - if desired. This would then replace the normal triggering process. |
+ | Some situations in which this could be used are as follows: | ||
- | Some situations where this could be used are: | ||
+ | * User wants to bypass the NovoMotion trigger | ||
+ | * User wants to add schema interaction to an ECA | ||
+ | * File updates occur multiple times and updates to the schema are only desired once | ||
+ | * User wants to execute the schema update from a specific process | ||
- | * User wants to bypass the NovoMotion trigger. | + | \\ |
- | * User wants to add schema interaction to an ECA. | + | Execution call for the subroutine: |
- | * File updates occur multiple times and updates to the schema are only desired once. | + | |
- | * User wants to execute the schema update from a specific process. | + | |
- | + | ||
- | + | ||
- | Execution call for the subroutine | + | |
CALL NOVO.EVENT.HANDLER(FILENAME, | CALL NOVO.EVENT.HANDLER(FILENAME, | ||
+ | \\ | ||
Definition of arguments: | Definition of arguments: | ||
Line 44: | Line 43: | ||
+ | \\ | ||
- | + | [[main_page|NovoMotion Outbound | |
novo_event.handler.1612471361.txt.gz · Last modified: 2021/02/04 15:42 (external edit)