Release Notes for the Cisco CMX Engage Release 3.2.16
Release Month: September 2018
This document describes the new features, enhancements, resolved issues, and open issues for the Cisco CMX Engage Release 3.2.16. Use this document in conjunction with the documents listed in the “Support” section.
The CMX Engage is a location intelligence, digital customer acquisition, and multi-channel engagement platform that enables companies to connect, know, and engage with visitors at their physical business locations.
The major features of the CMX Engage 3.2.16 release are as follows:
Provision to view the network synchronization status for each Meraki network.
New CMX Engage user role, “Reporting Analyst” with access to location-specific reports.
The following new features are added to the CMX Engage Dashboard:
Meraki Network Sync Details
The CMX Engage now provides the network synchronization status for the Meraki networks. A new link “Meraki Network Sync Status” is provided in the SSIDs section. You can view the last synchronization time for each Meraki Network.
The “Meraki Network Sync Status” window also provides a Search feature using which you can search for a specific network.
New CMX Engage User Role-Reporting Analyst
The CMX Engage now provides a new CMX Engage user role, “Reporting Analyst. In the “Invite a User” window, the new user role, “Reporting Analyst” will be listed in the “Privileges” drop-down list. You can specify the locations for which the user must be provided access.
For a “Reporting Analyst” user role, only Reports will be shown in the CMX Engage dashboard. The reports are shown only for the locations for which the user has access rights.
Table 1 Resolved Issues in the CMX Engage 3.2.16
CMX Engage Dashboard
For CUWN-WLC wireless network, when adding a WLC Controller, an unconfigured network group is not created if all the APs get grouped under any network. So, newly added APs without proper naming conventions were not getting added to the CMX Engage.
Now when adding a WLC controller, an unconfigured network group is created with “0” APs, even if all the APs are grouped under some networks. So, if any new AP is added to the WLC without proper naming convention, that AP gets added to the unconfigured group during network synchronization.
When adding a Meraki network to the location hierarchy, the time zones in incorrect format are also getting added to the location hierarchy.
Now, the CMX Engage validates the time zone format, and if found invalid, the default time zone “GMT + 00.00(UTC)” is assigned for that network in the location hierarchy.
In Location hierarchy, the APs with invalid MAC Address format are also getting added to the location hierarchy.
Now, the CMX Engage rejects the APs with invalid MAC address format, and they are not listed in the location hierarchy.
In the “Access Code” window, the calendar icon to specify the validity period for the access code is not displayed.
The Calendar icon is displayed now using which you can specify the start date and end date for the validity period of the access code.
CMX Engage Runtime
The session expiry duration specified in the Captive Portal rule is not considered, and the captive portal is displayed even when the customer connects to the SSID within the session duration. This issue is occurring only when multiple redirection happens.
Now the internet is provisioned without showing the captive portal if the customer accesses the portal within session duration specified.
Table 2 Open Issues in the CMX Engage 3.2.16
There are no open issues for this release.
You can access the support documentation using the Help button in the CMX Engage Dashboard.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.