Overview

System Actions allow for configuring email notifications. Notifications are triggered based on a specific trigger event and can be configured to be sent to different recipients.

System Actions are configured under Admin > System Actions in the navigation menu.

Notifications that have been sent by nVIRO can be viewed on the Admin > User Notifications screen. This screen can be filtered to only view notifications sent by a specific System Action. This can be useful for auditing whether a system action has been configured to send notifications correctly under the desired scenarios.

Trigger Types

System Action notifications can be triggered in either Real Time or part of a Batch Nightly process.

• Real Time triggers happen immediately as records are added or updated by a user, or some other user-initiated action. 
• Batch Nightly triggers happen as part of a nightly batch process that checks date values on specific records. 

The image below show an example of a Batch Nightly system action that has been set up to send a notification 5 days before a submission's processing deadline date is reached:

See the Trigger Events section below for more information.

Priority Ranking

In the System Actions List screen, each system action will display a Priority ranking. Priority is a system calculated value. The notification generation logic will always select the highest ranked notification that matches the criteria of the entity to which the notification relates (e.g. program area, entity type, etc).

Imagine three scenarios:

1. Submission Status Change Notification - Program Area =  (none) , Action Type filters = (none) (generic) - Priority = 3
2. Submission Status Change Notification - Program Area = "Air Quality",  Action Type filter =  (none) (more specific) - Priority = 2
3. Submission Status Change Notification - Program Area = "Air Quality",  Action Type filter = "Renewal" (very specific) - Priority = 1 

So if a submission's status changes for a Resources permit whose Action Type = "New" then #2 will be sent since it does not meet the criteria of #3.
So if a submission's status changes for a NPDES permit then #1 will be sent since it does not meet the criteria of #2 or #3

Trigger Events

System Action notifications can be set up to trigger on any of the following events

Note: All Application/Request triggers also fire for Schedule submissions.

Filters (System Action Entity Types)

System Actions can be filtered to trigger on only a subset of data. The available filters for each functional area are listed in the table below. If a functional area is not listed, there are no filters available.

Notification Recipients

Each notification can be set to be sent to a different recipient based on the recipient's role.

The table below lists the available recipient types for each different functional area