Release Notes for the Cisco CMX Engage Release 3.2.6
Release Month: November, 2017
This document describes the new features, enhancements, resolved issues, and open issues for the Cisco CMX Engage Release 3.2.6. 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.6 release are as follows:
No longer capture the data such as profile URL, profile image, and so on for social authentication.
Captures FB access token for Facebook authentication.
Upgraded the client side framework to RiotJS to optimize the captive portal loading speed.
The following enhancements are made to the CMX Engage Runtime:
For Social authentication, the following changes are made:
Removed the fields such as profile URL, profile image, and so on for the social subscriber data and acquisition logs.
Added FB access token to subscriber data and acquisition logs.
Client Side Optimization
For the captive portals, upgraded the client side framework to RiotJS for optimizing the captive portal loading speed.
Table 1 Resolved Issues in the CMX Engage 3.2.6
CMX Engage Dashboard
On editing a group, the group ID created for that group is removed.
If CMX SSID is available, cannot import a Meraki SSID with the same name.
Cannot import a SSID name that starts or ends with a pipe character.
For SMS notifications, space in the text editor is considered as unicode character.
Table 2 Open Issues in the CMX Engage 3.2.6
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.