Variable triggers
Variable triggers are based on trigger variable statements, and not on application, window or screen behavior. A trigger variable stores data obtained in triggers that can be used as a passback value, or as part of criteria that determines if a trigger is fired. Variable triggers work in conjunction to Screen triggers, window triggers, and system triggers.
Example: Varible triggers for Fraud compliance
A credit card company offers customers the ability to take small loans against their line of credit. According to company policy for compliance, all applications from customers in excess of $10,000 must be checked against the fraud database before the application is submitted. What managers have discovered is that the loan officers often forget this step and the officer has to run the check after submitting the application which delays the loan application process.
To prevent this, Sidney the DPA manager has created triggers. First she creates a screen content trigger which will look for the loan amount requested. If the amount is over $10,000, the trigger fires. When the trigger fires a trigger variable (FraudCheckRequired) is created. Its value is "true". This variable and value are saved in the DPA database. Three pages in the application later, there is a button for the loan officer to click in order to query the fraud database. When this page opens, DPA fires another screen content trigger which evaluates the FraudCheckRequired variable. If this variable is "true" a popup message is sent to the loan officer reminding him or her to check the fraud database.