2020.4 Release Notes

Notifiers and Activators

When creating outgoing webhooks, you can now include location-based variables in the Body field. See Webhook Notifier.
When creating outgoing webhooks, you can now include time and date information, via variables, within the Body field. You can also control the formatting with the Date Format and Time Format fields. See Webhook Notifier.

You can now send your notifications that use Response Option actions via email, SMS, and mass dialers. See Setting up Twilio and Clickatell for use with Response Options and Creating a Response Options Notification. See Email Notifier for information on how the notifier works with sending response options.
Revolution no longer requires a Mobile license to handle responses to notifications via Response Options. This is now handled with the CloudConnectPlugin, as tracked in the System Status page.
You can now view all responses to a notification when viewing the details of a Sent Notification. They are now collected in the Responses tab, accessible at the top of the notification details page. See Sent Notification Responses Tab.

You can limit the activation of a notification based on the location of a trigger. You accomplish this by specifying an area when selecting your triggers. See Restricting Triggers to a Geographic Area.
The {cisco.Geolocation} text variable now returns more information from your CUCM configuration. See Configuring CUCM Geolocation

When viewing details about Sent Notifications, you can review location and coordinate information for contacts and endpoints.

You can now upload images representing your building floor plans into Revolution. You will then see these images in several areas of the UI when working with maps, including sending notifications from the Endpoints Map on the Dashboard, creating Areas, and placing endpoints in the Endpoints window. See Floor Plans.

The Messages icon in the toolbar will now notify you (by adding a green dot to the icon) that an update to your install of Revolution is available.

The Endpoints window supports compound filtering, allowing you to filter the endpoint list by multiple columns. See Filtering Endpoints.
When you bulk edit endpoints from a CSV file you can now match your data to DN values, in addition to IP Address and MAC. See Updating endpoints from a CSV file.
You can now define location information for your endpoints, which will be used by text variables in your notifications. See Editing IP Device Details.

When importing users through Active Directory or CSV you can now define whether the imported users receive a one-time use password for their first login. See Import user accounts from Active Directory and Import users from a CSV file.

Sites now support location information. When you add location information to a site, your location-based variables in your notifications will follow this priority:
1. Location information associated with the specific endpoint.
2. If the endpoint does not have location information, the variables will use the location information of the Site.
3. If neither the endpoint nor the site have location information, the variables will return null values.

The Clear notification from display on completion option in the Message Details section of a notification will now clear notifications sent to the DNC. See Clearing displays after a specified time.
The topic Configuring DNC Settings on Windows defines the ways you or your admin can set up your DNC installation.
The DNC on Windows can now show notifications when your screen is locked. Your administrator will grant permission for this upon installation of the client. See Using the Desktop Notification Client and Configuring DNC Settings on Windows.
The DNC on Windows now uses the heartbeat interval and listen port specified in the Desktop Notifier settings for each Revolution server. Previously, you could define these values within the DNC, but that is no longer the case.
When installing the DNC on Windows from the command line, you can now specify additional command line arguments. See Automated Installation.

The Cloud Timeout field in the Network global settings controls how long a module or plug-in must be inactive before Revolution reports an error. See Network in Global System Settings.