Event Notifications

In addition to the regular Event view, you can customize and set up if and how you would like to be notified in case of events.
When an event occurs, it is categorized, which in turn triggers the assigned actions.
[Alternatively, you can choose to leave the useful defaults as provided.]

By default, all events are shown in the Events view [except for category Validation].
First, learn more about »Events

▪Go to the menu Preferences > Event Configuration...
[Keyboard shortcut: Ctrl + Alt + E]

▪New Event Configuration - Resets any configuration of Actions, Categories, or Events that may have taken place and restores the default settings. All custom actions will be deleted and the event and category mappings will be reset.
[Keyboard shortcut: Ctrl + N]

▪Open Event Configuration... - Loads a previously saved Event Configuration file [of the file type *.revcx].
[Keyboard shortcut: Ctrl + O]

▪Save Event Configuration - Stores an Event Configuration in an external file [of the file type *.revcx] in order to preserve it.
- Sensible information [such as, user name, password, and command line commands] will be saved and encrypted with the Advanced Encryption Standard AES 256.
[Keyboard shortcut: Ctrl + S]

▪Save Event Configuration As... - Stores the Event Configuration as a separate, duplicate file. And allows you to choose a different name.
- Sensible information [such as, user name, password, and command line commands] will be saved and encrypted with the Advanced Encryption Standard AES 256.
[Keyboard shortcut: Ctrl + Shift + S]

▪Close - Closes the Event Configuration window.
[Keyboard shortcut: Ctrl + F4]

Actions allow you to define the kind of notification or action that should be triggered when an event occurred.

By default, events are always shown in the Events view [except category Validation].. Learn more »Events

	Add Action - Creates a new action.
	Remove Action - Removes the currently selected action. [Select an action via the selection field to the right. See Select Action below.]
	Edit Action Label - Allows you to change the name of the action.
	Select Action - Allows you to choose which action configuration you would like to see or edit.

Allows you to let the software periodically send e-mail notifications to you automatically.
A message includes a text file [of the file type *.txt] in the attachment which contains all events that occurred.

You can choose to have messages sent only in case events were reported or always; even if no events occurred.
Configure all settings as described below.

▪Receiver Address - Enter the e-mail address or address to which send the automatic reports [for example, receiver@company.com].
- Enter one e-mail address or enter several addresses and separate them via spaces [ ], commas [ , ], or semicolons [ ; ].

▪Server - Enter the e-mail server's address from which e-mails are sent [for example, mail.company.com].
- Port - Enter the communication port that is used by your e-mail server.
[Any input will be saved and encrypted with the Advanced Encryption Standard AES 256.]

▪Sender Address - Enter the e-mail address from which e-mails are sent [for example, maintenance@company.com]
[Any input will be saved and encrypted with the Advanced Encryption Standard AES 256.]

▪User Name - Enter the name that is used to establish the connection to the e-mail server.
[Any input will be saved and encrypted with the Advanced Encryption Standard AES 256.]

▪Password - Enter the password that corresponds with the user name. Any input will be hidden.
[Any input will be saved and encrypted with the Advanced Encryption Standard AES 256.]

▪Send Every - Defines how often e-mail messages are sent. Enter any number and choose the time interval.
- Valid values range from 1 minute to 12 months. The default value is 1 day.
- Starting At - Allows you to define the start date, when the software begins sending messages. Set up the date and time accordingly.
- If the date is set to a past point in time, one message will be sent retroactively.

▪Send an attachment with the following text, if no events occur - If enabled, allows you to receive messages even if no particular event has occurred.
- Enter any text in the input field. [By default, it includes No events occurred in the recent interval.]

▪Subject - Enter the subject line of e-mails. [By default, it includes Status Report]

▪Body - Allows you to enter any additional text in addition to the automatically generated header and footer created by the software.

▪Test - Directly tries to send an e-mail [with the current settings] in order to test the functionality and server settings [without having to wait until an event occurs].

Allows you to execute commands in the PowerShell.
PowerShell is an integral tool of the Windows operating system for advanced scripting. It is already installed and available with Windows 10.

▪Commands - Enter the command which you would like to execute.
- See below for examples.

▪Test - Directly executes the entered command in order to test its functionality [without having to wait until an event occurs].

Executing Shell Scripts via the PowerShell provides numerous possibilities. Here are several examples on how to use these capabilities:

▪Start another software application, such as MADRIX 5:
start-process -FilePath "C:\Program Files\MADRIX5\Madrix.exe"
[C:\Program Files\MADRIX5\Madrix.exe is the default installation directory. MADRIX 5, in turn, could for example automatically start a Cue List, run a script or macro, or control a lighting fixture as a status light.]

▪Start a batch file:
start-process -FilePath "C:\Test\MyTestFile.bat"
[C:\Test\MyTestFile.bat define the directory and specific file to launch. Batch files are scripting files that can start a more complex process or several tasks at once.]

▪Write into a text file:
"Alert" | Out-File C:\test\process.txt
[Alert is the string that is written into the file. C:\test\process.txt define the directory and specific file to write into. Directory and file need to exist before the functionality can be used. MADRIX 5 Script can read from text files, for example.]

▪Sending HTTP requests to MADRIX 5:
Invoke-webrequest -URI http://10.0.0.49/index.html?SetStorage=S1P5
[See the MADRIX 5 HTTP Remote Control Commands at »help.madrix.com for more information.]

▪Sending HTTP requests to MADRIX AURA:
Invoke-WebRequest -URI http://10.84.0.8/remote.cgi?Intensity
[See the MADRIX AURA User Manual at »help.madrix.com for more information.]

▪Combining several commands into a single HTTP request [for MADRIX 5 for example]:
Invoke-webrequest -URI http://10.0.0.49/index.html?SetAudioOutputMute=1"&"SetBlackout=1
[The & character needs to be embedded into "" regarding PowerShell scripting.]

The Categories tab allows you to define different classes of events. This allows for more granular filtering and sorting [in the Events view, for example]. And you can set different notification settings [actions] for each category.

All categories are listed alphabetically.
By default, 4 categories have been defined [Critical, Info, Validation, Warning].
Configure categories as described below.

2] Enter a name for the new category. Confirm with OK. Abort the process via Cancel.

2] Change the current label or enter a new name. Confirm with Enter. Abort the process with Cancel.

Please note: Any event that was assigned to a category that has now been removed is no longer assigned to a category.

	Assign Action - Assigns an action to the particular category. - A new window opens to choose the action. Confirm with OK. Abort the process via Cancel. - A specific action can only be assigned once per category. - You can assign any number of actions. - Display refers to in-app notifications in the Events view.
	Remove Assigned Action - Removes the currently selected action from the category again. Select the action first.
	Prioritize Assigned Action - Allows you to rearrange assigned actions. Actions will be processed consecutively. Actions higher in the list will be processed first.
	Deprioritize Assigned Action - Allows you to rearrange assigned actions. Actions will be processed consecutively. Actions lower in the list will be processed last.

The Events tab allows you to assign events to the different categories.
When an event occurs, it is categorized, which in turn triggers the assigned actions.
All possible events are listed here.

Domain	Shows the type of events.
Label	Shows the description of each specific event.
Category	Can be edited and allows you to assign each event to one of the categories you have defined. - Assign an event to a category [or leave the defaults]. - You can also choose None, which means that the event does not trigger a notification. - You can select multiple entries in the list to change their category all at once. Select the entries in the list first. - Select File > New from the menu if you would like to restore the default settings.
Description	Shows an in-depth explanation of the event.

▪Right Mouse Click - Perform a click with your right mouse button on an entry.

Copy Selected Cell To Clipboard	Copies the currently selected cell [that is, single information] into the clipboard/temporary memory. [Keyboard shortcut: Ctrl + C]
Copy Selected Rows To Clipboard	Copies the currently selected line or lines [that is, all parameter information] into the clipboard/temporary memory. [Keyboard shortcut: Ctrl + Shift + C]

▪Search - Enter any text in order to search all parameters in the list.
- Any device/line that includes the search term will be shown. All others are temporarily filtered out.
- Terms can be case-insensitive. You don't have to use capital letters.
- Feel free to use terms that are incomplete. For example, mad will include results for MADRIX.
- You may specify certain columns by using a colon [:].
- For example: eve:max shows all lines that include events referring to maximums by referencing the column Event, for example.

In order to monitor if the connection to RDM devices/sub-devices/fixtures has been lost, use the following events:

▪DeviceConnectionRestored
[Indicating that the connection has been restored successfully.]

In order to monitor if the connection to interfaces has been lost, use the following events:

▪InterfaceConnectionLost
[Indicating that the connection has been lost. The average time it takes before such an event is registered is: 3 minutes.]

▪InterfaceConnectionRestored
[Indicating that the connection has been restored successfully.]