Open

Overview

Alert Router

• Allows oneWeigh users to send Audit Log entries as instant alerts or daily summaries via email.

• They also allow for daily summaries to be posted to a specific file location without email being setup.

• Uses oneWeigh Communicator to send alerts

oneWeigh Communicator

• oneWeigh Communicator must be enabled for alert router to work.

• It is also required to be run throughout the day/evening when you wish to receive alerts.

• If ticket post is closed at 12:01AM the daily summary and export files will not be posted until ticket post is run again.

oneWeigh Audit Log

• Alert Router leverages all the existing search and filtering capabilities within the Audit Log

Setup

Overview

Navigate to ‘ONE’ -> Audit Log

Open

• At this point you will have two options to the right one is greyed out and the other is available to click on.

• You MUST setup your Alert Router Settings first, prior to creating Alert Router Tables

Server Configuration

**SMTP Setup will need to be verified from the customer or their IT department – we have a set of best practices outlined below**

• Enable Secure Socket Layer: Yes

• SMTP Host: localhost

• Port Number: Typically, 587 but if that does not work try 465

• Host User: Username that would be connected to the email account. IE Ryan.Quirk

• User Password: Password for that account

• Default “From” Email Address: The account that sends out the alert router email. IE Ryan.Quirk@culturatech.com

• One this is complete you can click ‘Ok’. These settings can be changed at any time, but this must be configured before you can setup Routing Tables.

Alert Routing Table

• There are 3 different alert types that you can set in the Router.

Instant

• These alerts are meant to be used to notify someone immediately via email when a specified action occurs.

• Use these sparingly, or else you will get flooded with emails.

• In the Recipient Email(s) textbox, enter the email address(s) who should receive the email

• To add more recipients, simply type in another email address after the first, separated with either a comma or a semicolon (this does not need to be the same after every email address added).

• Valid input: email1@host.com, email2@host.com; email3@host.com

• It is important to note that the “Recipient Email(s)” textbox will hold 200 characters. This will be enough for most customers, but if more recipients need to be added one can create an identical email entry with the remaining email addresses.

• In the scenario below I have selected to receive an instant (A) alert for any exceptions (B) handled by Self Check-In (C)

Instant Email Example:

Daily Summary

• Sends a single email with an attached csv file of every occurrence of these requirements of the previous day when Ticket Post is running

• In the Recipient Email(s) textbox, enter the email address(s) who should receive the email

• To add more recipients, simply type in another email address after the first, separated with either a comma or a semicolon (this does not need to be the same after every email address added).

• Valid input: email1@host.com, email2@host.com; email3@host.com

• It is important to note that the “Recipient Email(s)” textbox will hold 200 characters. This will be enough for most customers, but if more recipients need to be added one can create an identical email entry with the remaining email addresses.

• Highly suggest using these reports to collect larger amounts of data in a single email. Such that if Scale A closes for the weekend. At the end of the day on Friday, everything is shutdown, including ticket post. On Monday morning, once ticket post is turned back on, the daily email with all the information from FRIDAY will send. This prevents the email recipients from receiving too many emails.

• In the scenario below I have selected to receive a Daily Summary (A) alert for any exceptions (B) or processed (C) events handled by Self Check-In (D)

Daily Summary Example:

Daily Summary Attached CSV File:

File Export

• Creates a single file with all the selected information in the noted folder once a day.

• Same as the Daily Summary this is posted at 12:01AM – if Ticket Post is running. However, if Ticket post is closed then the export will be created the next time ticket post is opened.

• You can copy/paste the file path in or use the search tool to browse for the desired network path.

• In the scenario below I have selected to receive a File Export (A) alert for any error (B) or exception (C) events handled by the Printer (D) or Manual Weights (E). The file created will be placed in the designated File Export Location C:\Apps\AGRIS\Alert Router (F).

Review

• It is important to realize that to send ANY type of alert, Ticket Post MUST be running • In the Routing Table, both Alert Type and the Exception Levels columns are abbreviated.

• Alert Type: I – Instant Email, D – Daily Summary Email, or F – File Export

• Exception Levels: E – Error, X – Exception, P – Processed

• To delete an entry simply highlight the line you want to remove and click ‘Delete’

• As of now, there is no way to search for an email address in the Recipient(s) column. However, you can scroll through the list of emails, using the arrow keys, in the email details page. One can get there by highlighting the email entry on the alert router table, then clicking “Edit” at the bottom of the page.

• There is no need to save the Routing Table itself, as each entry of the table is saved after a successful add, edit, or delete. Once, one is done making changes to the Routing Table it is safe to close the page.

By: Travis Jerke and Curtis Green