Release Notes for the Cisco CMX Engage Release 3.2.14
Release Month: July, 2018
This document describes the new features, enhancements, resolved issues, and open issues for the Cisco CMX Engage Release 3.2.14. 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.14 release are as follows:
Support for Cisco Catalyst 9800 Series Wireless Controller.
Support to include country code in the iOS App URL in the Get Apps module.
Support to include custom variables in the Landing Page URL in the Authentication module.
Support to capture gender and age details of the customer during the Facebook authentication based on new Facebook app guidelines (runtime).
The following new features are added to the CMX Engage Dashboard:
Cisco Catalyst 9800 Series Wireless Controller Network Support
The CMX Engage now supports Cisco Catalyst 9800 Series Wireless Controller. In the CMX Engage dashboard, for Cisco Catalyst 9800 Series Wireless Controller with Cisco CMX, you can use the wireless network CUWN-CMX. For Cisco Catalyst 9800 Series Wireless Controller without Cisco CMX, you can use the wireless network CUWN-WLC.
The following enhancements are made to the CMX Engage Dashboard:
Country Code Support for iOS App URL
The “Get Apps” module in the captive portal now supports to add country code in the iOS app URL. The country code mentioned in the URL is saved in the CMX Engage portal configuration. Previously, the customers were facing issues to access the country-specific iOS app URLs. You must define the country codes based on the iOS country code specifications.
Sample iOS App URL with country code : 'https://itunes.apple.com/ br /app/rold%C3%A3o/id1355690232?l=en&mt=8", where “br” is the country code.
Custom Variable Support for Landing Page URL
In the captive portal, the “Landing Page URL” text field in the “Authentication” module now supports to include custom variables in the URL. This enhancement enables you to add URLs with custom variables.
CMX Engage Runtime
The following enhancements are made to the CMX Engage Runtime:
Facebook Extended Permission
To incorporate the new Facebook App guidelines on 01 August, 2018, the CMX Engage runtime is enhanced to obtain permission for fetching the gender and age information of the customer during Facebook authentication.
Table 1 Resolved Issues in the CMX Engage 3.2.14
CMX Engage Dashboard
In the Captive Portal Rule, for the session duration option, the session duration can be configured only for maximum 99 days.
This issue is resolved by enabling to configure the session duration up to 365 days. Even if you are mentioning the session duration in hours or minutes, you can mention a duration equivalent to 365 days. This is applicable for session duration option in the “Show Captive Portal” and “Seamlessly Provision Internet” sections of the Captive Portal Rule.
Inappropriate message “Invalid Link” is shown, if the “Accept Invitation” button is clicked after activating the account.
Now if the “Accept Invitation” button is clicked after activating the account, the message “The account is already activated” is shown.
For the CUWN-WLC wireless network, if AP names are not grouped by prefix when adding the WLC controller, then not able to group those APs later using prefix.
Now the unconfigured APs with same prefix, which are skipped to group when adding the WLC controller, can be grouped later to add networks.
In the Reports section, the Tagging Tend graph for the Profile Rule and Engagement Rule are not shown based on the CMX Engage user’s time zone as expected.The graph is shown based on the customer’s zone.
Now the Tagging Tend graph is shown based on the CMX Engage user’s time zone.
CMX Engage Runtime
There is no restriction on the number of SMS that can be sent to a customer for SMS authentications. This can lead to spamming of messages, which is a security issue.
This security issue is fixed by limiting to send only maximum 3 successful messages to a customer per minute.
Table 2 Open Issues in the CMX Engage 3.2.14
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.