Triggers in the Configurator
In a business rule created in the Configurator In Application Design, the graphical interface for configuring a business rule by creating component sets, each containing component blocks that are run when a particular trigger event occurs., a trigger
A means of running an action, rule, or data service. Includes a trigger source if interactive (such as a button, a prompt, or a form) and a trigger event (such as clicking a button, entering text at a prompt, loading a form, or submitting a job). For example, you can specify a particular button as a trigger source that Data Providers can click to perform a query of a database. is the part of a component set that controls if and when the component blocks in that component set are run. Each trigger is associated with an event, and the component blocks in a component set are run only when the event specified by the trigger occurs.
Note: In the Business Rule Summary for a particular business rule, the name of each trigger must be unique.
Trigger Event or Type | Purpose | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Job Submission |
A Job Submission trigger causes the component set to run during the job submission phase, before the job is queued for printing. This event occurs for each job in a stacked job. As a best practice, it is recommended that you use this type of event to run database or other process intensive component sets. |
||||||||||
Job Printing |
A Job Printing trigger causes the component set to run when a job is removed from the queue to be printed. |
||||||||||
Label Printing |
A Label Printing trigger causes either the component set or the data sources defined in Label Design Best Practice In most cases, it is recommended that you use the Label Printing trigger to run Format Date/Time component blocks. |
||||||||||
Error |
An Error trigger causes the component set to run when an error occurs during the processing of any component set in the business rule. |
||||||||||
Custom |
A Custom trigger causes the component set to run when the Custom event specified by the trigger occurs. Custom events typically occur due to the action of a component block or a business rule component. Some examples of Custom events include when a condition is true, when a condition is false, when a row of data from a database is processed, when an iteration of a repeating action occurs, or when an error occurs. Important! Before a Custom trigger can function, either a component block or a programmer must define the associated Custom event in the business rule. The exception to this approach is that you can use a Run Another Component Set block or a Run Another Business Rule block to run a component set that has a Custom trigger even if no associated Custom event exists. The following types of component blocks define Custom events. If you use one of these event names as the name of a Custom trigger, then the component set associated with the Custom trigger runs when the event occurs.
|
Note: If you require that a business rule have additional capabilities or flexibility beyond what is possible by using Configurator, a programmer can use XML to develop a business rule. For more information, see Implementing Business Logic.
Tip: For assistance with a business rule that you have created or to have Loftware create business rules for you, contact Loftware's Professional Services Group.