Recurring System Triggers
Recurring Triggers are a new type of trigger introduced in 2021 as part of the Logiforms Enterprise Trigger Management Addon available exclusively on Enterprise Plus Plans.
Recurring triggers are made up of a set of actions that can be run on a preconfigured schedule. This can be hourly, daily, weekly, the first and last day of each month, or every year, for example.
When you set up a set of actions to run, you also create the lookup filter that determines which records will be processed. This filter includes options to select records based on the number of days before or after a date, if a date field in a record is tomorrow, yesterday, next week or x number of days away. Using these filtering clauses and daily recurring Actions, you can set up event reminders, follows ups, automated export and API calls, and much more.
Creating a new Recurring System Trigger
From the Enterprise Trigger Manager Dashboard or main menu, select "New System Trigger". Once the wizard opens (shown below), choose "New Schedule Execution Trigger":
Next, the wizard will ask you to give the trigger a name and configure settings related to logging and cascasing Trigger, PDF and Webhook execution
| Property | Details |
|---|---|
| Trigger Name | The name of the trigger |
| Enable Logging | Check this box if you wish to log each trigger action execution. If you do not check this, the real time monitor will still show execution logs and the start and end of each execution is still logged including the number of actions executed and which actions executed. However, when unchecked the individual action logs will not be recorded. |
| Do not run other form triggers on Update | If your set of actions updates the records and you DO NOT want your other form trigger actions to run, check this box. |
| Do not generate PDFS on Update | Check this box if you do not want PDFs to be generated when records are updated. |
| Do not run Webhooks on Update | If your form uses webhooks, check this box to skip processing of those webhooks when records are updated. |
| Target Form | Select the form which includes the records that will be processed EACH time this trigger runs. |
| Lookup Rule |
The Lookup Rule defines which records be processed in each batch. For example, your trigger might be setup to run at 5PM each day and the lookup rule could be configued to find any COVID health screening form entries that were still marked as "PENDING", you could then automate an SMS message and move those records into a follow up quueue. |
New Lookup Rule Operators!
We've also added a ton of new date based lookup operators that can match records based on dates. For example, you can now find all records where the due date is less than X days from now.
Schedule Settings
Next, configure the schedule and frequency for the trigger.
Schedule Range
Next, define the start and end dates for the trigger. You may also select the No End Date option.
Trigger Actions
Finally, add the individual actions that will execute when this trigger runs. Note, that each trigger action may have its own rule to bypass procesing based on specific values in the record. Adding trigger actions here, is the same as adding standard form trigger actions.
When you click Finish, the Recurring Trigger will be created and will be available in the Central Trigger Management view. Read more about viewing execution logs here.
You can also view the recurring trigger schedule in the Recurring System Triggers Calendar. If you need to pause a recurring scheduled task, you can right click on the trigger in the Central Trigger Management View and select pause. You can re-enable the trigger as needed. Recurring triggers can be edited any time (except when they are running). Clicking on View Execution Details will open the Enterprise Trigger Management Log Window.
Editing Recurring System Triggers
Recurring System Triggers and their actions can be edited any time that they are not running.Matching All Records in a Lookup Rule
When you want a Recurring System Trigger (or a Lookup Data filter) to match every record in a form, use the system RecordID field rather than LFUUID:
- Set the Lookup Rule to RecordID is greater than 0 (
RecordID > 0). - Do not use LFUUID is not empty or LFUUID is empty in a Lookup Rule. Because
LFUUIDis stored in the database as a UUID (unique identifier) column rather than a text column, comparing it to an empty string with is not empty or is empty fails with a database conversion error and prevents the trigger from running.
Sending a Single Daily Summary Email Instead of One Email per Record
Symptom: A Recurring System Trigger sends a separate email for every matching record (for example, 28 emails when 28 records match), or the repeating summary table inside the email is blank.
Cause: A Recurring System Trigger executes its actions once for every record matched by the trigger's Lookup Rule. In addition, a repeating table in an email body only populates when its [LookupName:...] wildcard prefix matches the lookup name configured under Lookup Settings in the Email Notification Profile.
Fix:
- In Enterprise Trigger Manager, edit the Recurring System Trigger and set its Lookup Rule to match a single record, such as RecordID = 1 (using the
RecordIDof any existing record on the form). Because only 1 record matches the trigger's Lookup Rule, the trigger runs its email action only once per scheduled cycle. - Open your form's Email Notification Profile (Email > Notifications) and go to Lookup Settings (see Using Lookup Data).
- Set the lookup name (for example,
Summary) to match the prefix used in your email body's repeating region tags ([Summary:Start Repeating Region]...[Summary:End Repeating Region]). If you rename an existing lookup, re-insert or re-save the lookup fields in the email body so they bind to the form fields. - Edit the lookup filter inside Lookup Settings to match the records you want listed in the summary table, such as RecordID is greater than 0 for all records or your specific date/status criteria (do not use LFUUID is not empty).
- Click Finish to save the Notification Profile and the Recurring System Trigger.
0 Comments