Register Interface Events
Once the basic interface has been established, an Interface Designer can add interface events to interfaces using the Interface Events page.
Supported event types are:
Events run sequentially based on their priority; those with the lowest priority run first. There are 2 cases where events run simultaneously:
- If an event submits a job to the job queue (i.e., runs in the background), the next event immediately starts running as soon as the job from the previous event has been added to the job queue.
- If there is not a WAIT parameter passed to an interface CommandExec event, the next event is immediately started once the CommandExec has started running.
Events that run simultaneously, i.e., if an event submits a job to the background, the next event does not wait for the previous job to finish. To configure events to run sequentially, refer to Run Interface Events Sequentially.
To help with performance, it is recommended to have more interfaces with fewer events each than to have several stored procedures registered to one interface.
Was this article helpful?
Sorry about that.
Why wasn't this helpful? (check all that apply)
Thanks for your feedback.
Want to tell us more?
Send an email to our authors to leave your feedback.
Great!
Thanks for your feedback.