Trigger settings
The Settings tab allows you to set
parameters for the trigger that provide specific execution
processing such as the number of triggers that can be
processed at the same time.
Parameter descriptions
Parameter |
Description |
---|---|
Max in Progress |
Sets the number of trigger instances
that are allowed to execute
concurrently. The default value is
one. |
Max Exec Time (ms) |
The maximum execution time for the trigger, in milliseconds. If the trigger execution exceeds this time, a warning message is logged in the Exceptions Log (even though the Reporting parameter might be set to off). This warning message in the Exceptions Log is for informational purposes, it does not end or change the trigger's execution. |
Reporting |
The trigger reporting option
controls when a trigger report is
generated and written to the Reports
Log. |
Apply reporting settings to subtriggers |
An option to have the trigger
reporting setting selected for this
trigger applied to all "called"
subtriggers. If selected, the trigger
reporting selection (On, Off, etc.) is
passed to a subtrigger that is "called"
using the Execute
SubTrigger action. This
passing of the reporting selection
applies to all levels of called
subtriggers. |
Queue Size |
The number of trigger instances that
can be queued for later execution when
the number of concurrent trigger
instance execution reaches the
Max in Progress
parameter. Trigger instances queued are
executed once another executor becomes
available (its trigger instance ends
execution). The default value is blank,
which is the same as a zero, which
indicates the queue is disabled. |
Editor mode |
The trigger editor to use when editing this trigger:
|
Editor Layout (Global) | A Global setting, for all triggers, for the trigger editor's display layout style. |
Use of trigger settings during development, debug and production
As an application's triggers are developed and debugged, the settings can be used to aid the development process and to understand a trigger's execution path.
Once the application is put into production, the settings can be monitored to understand how the triggers are executing in different production environment scenarios.
For example:
- The Reporting parameter can be set to On when developing a trigger and then set to Off before going into production.
- The Max in Progress parameter can be used to ensure that only one instance of a trigger is executing concurrently (value set to 1) or it can be used to allow multiple concurrent instances of the trigger to execute concurrently. Allowing multiple instances of a trigger to execute concurrently may require serialization or concurrency concepts in the trigger's application logic.
- The Queue Size parameter can be used to allow temporary spikes in trigger instances being scheduled for execution to be queued for later execution, instead of discarding the instances as an Overflow.
- An increase in a trigger's Overflow counter (in the trigger list in the project's tab on the Projects window) may mean that the Max in Progress and Queue Size parameters need to be adjusted based on the trigger's event frequency and the trigger's execution time.