Scheduled business rules
Introduction to scheduled rules¶
Business rules, ticket creation rules, and ticket closing rules are general purpose tools to automate as many tasks within the system as possible, saving time on repetitive maintenance and reducing human error. Business rules perform actions on datasets, e.g. setting an attribute's value or running a script. Ticket creation and closing rules automatically open or close tickets based on certain conditions.
While business, ticket creation, and ticket closing rules can be set to run after certain events, they can also be run automatically using schedules. Scheduled rules allow you perform actions at set times, making it easier to manage your data, and allowing you to optimize performance by scheduling actions during non-peak hours.
Administration > Rules > Schedules will take you to the Manage Scheduled Rules page, which displays a list view of all scheduled rules.
Table 1: List view contents
|Title||Title of scheduled rule|
|Run||When the rule runs (e.g. daily)|
|Rule||Business rule being run by this schedule|
|Last Run||When the rule was last run|
|Next Run||When the rule will run next|
|Active||Whether the scheduled rule is active. Inactive scheduled rules will not run.|
|Last Updated||When the scheduled rule was last updated|
Create a scheduled rule¶
- Navigate to Administration > Rules > Schedules.
- Click the Create Scheduled Rule button
- Fill in the following, then click Create
Table 2: New scheduled rule properties
|Title||Title of scheduled rule. The title will be displayed wherever the schedule appears in the UI.|
|Name||Reference name for queries and scripts. The name can contain only letters, numbers, and underscores.|
|Rule||Business rule, ticket creation rule, or ticket closing rule that will be run.|
|Run As||Allows you to select who the rule will be run as.|
|Active||Sets whether the scheduled rule is active. Inactive scheduled rules will not run.|
|Conditional||Allows you to enter a Groovy script that specifies additional conditions for running the rule|
|Execute pre-sync script||Allows you to enter a Groovy script to be run before the rule is started|
|Execute post-sync script||Allows you to enter a Groovy script to be run after the rule is completed|
|Run||Sets how often the rule will run (e.g. hourly, daily, weekly). The options below will change depending on what frequency is set, allowing you to specify exact times.|
|Accessible from||Specifies whether this scheduled rule will be available to all Brinqa applications or only the application you are currently administrating.|
Edit or delete a scheduled rule¶
Existing scheduled rules can be edited or deleted by clicking the Actions button that appears to the right on mouseover of the entry on the list view.