Rules and automations
Axon Records can automatically take action when certain events happen in the system, so your team spends less time on repetitive manual work. These automations are called "rules."
Contact your Axon representative or Axon Support to request rules be configured for your organization's specific needs.
What rules can do
Rules can be configured to perform the following actions:
| Category | Action details |
|---|---|
| Restrictions | Add a restriction to a report |
| Case management | Create a case from an incident report, or route a case to a specific unit |
| Case tasks | Add one or more tasks to a case |
| Notifications |
Send an in-app notification or email to specific people |
| Tasks | Assign a task, change a report's state, update a report's district, or delete comments on a report |
| Flags | Add a flag to a person's profile |
When rules can run
Rules can be configured to run when the following activities occur:
| Type | Activity details |
|---|---|
| Report | A report is created, approved, rejected, or moves into a different state |
| Task | A task is created or assigned to someone |
| Event | An event is created in Axon Standards |
| Profile | A profile is created or updated |
| Warrant | A warrant's status is updated |
| Schedule | Runs on a recurring basis, such as daily or weekly, instead of in response to a specific event |
Conditions
Conditions let you limit a rule so it only runs in specific situations instead of every time that activity occurs. For example, a rule can be configured to apply only to reports assigned to a certain district, or only when a person is added to a report and their age falls within a certain range.
Rules can include one or more conditions. If a rule includes more than one condition, you can choose whether all conditions must be true or whether any one of them is enough.
Available conditions include:
| Type | Condition details | Example: Only run this rule for... |
|---|---|---|
| District or site | The report or record belongs to a specific district or site | Reports from the Downtown district |
| Offense category | The report includes one or more specific offense categories | Reports categorized as burglary or theft |
| Case factor | The case has been tagged with a specific case factor | Cases tagged as gang related |
| Person age | The person on the profile falls within a specific age range | Profiles for people under 18 |
| Assigned user | The report or task is assigned to a specific person | Tasks assigned to a users in the Supervisors team |
| Charge | The report includes a specific charge | Reports that include a DUI charge |
| Restriction classification | The restriction being applied matches a specific classification | Restrictions classified as confidential |
Example rules
Here are a few examples of rules organizations commonly use. Your Axon representative can help you build something similar or design a rule specific to your workflow.
Notify a case owner when a warrant status changes
When a warrant's status changes to Served, Axon Records sends an in-app notification to all users in the Investigative Division. This notification appears in the Notification Center.
Create a case when a report is approved and route the case
When an incident report with a Case factor of "Arson" is approved, a case is created. The case is routed to the Arson inbox where it can be assigned to a Lead Detective.
Add a flag when a new profile is created
When a new person profile is created and the person is under 18, a "Juvenile" flag is applied to that profile.
Send a weekly digest to supervisors
On Mondays at 8:00 AM, a digest notification is sent to all supervisors summarizing their team's outstanding reports, so nothing falls through the cracks.
