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.13 release are as follows:
Data Capture and Opt In subscription support for “No Authentication” captive portals.
Provision to upload JSON file for CUWN-CMX for manually creating the location hierarchy.
Display of CMX Engage license information in the dashboard.
Display of DigitCert CA root certificate installation guidelines in the CMX Engage dashboard.
Support to add APs to zones without any APs.
Account security optimization by enforcing re-login after 4 hours.
Provision for repeat users to access internet from the captive portals with only “Help” and “Feedback” options enabled.
The following new features are added to the CMX Engage Dashboard:
Opt In Subscription and Data Capture for “No Authentication”
The authentication type, “No Authentication”, will now have the provision to Opt In for subscription and to configure Data Capture form. You can also configure to display the Data Capture form in the portal home page.
The following changes are made to the Captive Portal wizard to support these features.
To support Opt In subscription, the “Allow users to Opt in to receive message” check box is now available for “No Authentication” in the Authentication screen.
To support “Data Capture”, when you click “Next” in the Authentication screen, now the Data Capture screen is displayed.
To display Data Capture and User Agreements (Terms & Conditions) on the portal home page, a “Display Data Capture and User Agreements on portal home page” check box is displayed in the Authentication screen.
An authentication module appears for the “No Authentication” captive portals, if “Data Capture” or “User Agreements” is enabled, and the “Display Data Capture and User Agreements on portal home page” check box is checked. The name of the authentication module for “No Authentication” captive portals for various scenarios is as follows:
If “Data Capture” and “User Agreements” are enabled, the authentication module name will be ‘Data Capture”.
If “Data Capture” is enabled, and “User Agreements” is not enabled, the authentication module name will be “Data Capture”.
If “Data Capture” is not enabled, and “User Agreements” is enabled, the authentication module name will be “User Agreements”.
If both “Data Capture” and “User Agreements” are not enabled, the Authentication module will not be there.
Upload JSON Support for CUWN-CMX
The CMX Engage dashboard now supports to upload JSON file for CUWN-CMX to create location hierarchy manually. The CMX Engage new platform was not supporting to upload the JSON file.
The CMX Engage dashboard now displays the license details of your CMX Engage account. The details such as the CMX Engage account name (customer name), license type, license validity, and access points limit along with number of access points in use are displayed. The customer support e-mail ID is also displayed at the bottom of the window.
In the left pane of the CMX Engage dashboard, when you click the “User Account” icon, the License Information option is displayed.
If the CMX Engage account license is expired, when the CMX Engage user tries to login, the message “License Expired” is displayed.
However, the license information will be not shown for access code manager accounts.
CMX Engage Runtime
The following new features are added to the CMX Engage Runtime:
Opt In Subscription and Data Capture for No Authentication
The CMX Engage runtime now supports the Opt In subscription configuration and Data Capture form for “No Authentication” captive portals.
The following enhancements are made to the CMX Engage Dashboard:
DigiCert CA Root Certificate Guidelines
The guidelines to configure DigiCert CA root certificate required for WLC 8.3 or later is added to the CMX Engage dashboard.
In the CMX Engage dashboard, a new section “Install your CA certificate” is included in the “Configure SSID in CUWN - WLC” tab, which appears when you click the “Setup SSIDs in Meraki/CUWN” link in the SSIDs section.
Support to Add APs to Zones without APs
If an existing zone has no access points, you can now assign new access points to that zone. To support this feature, a “Modify Access Points” button is now available for the zones, without any access points. Even though, atleast one AP is required to create a zone, there are occasions that this AP gets deleted from the wireless network, and the zone will be without any AP. Previously, it was not possible to add access points to such zones.
To enhance the security of your CMX Engage account, a user session is now restricted to 4 hours. After 4 hours of log in, the CMX Engage user will be forced to re-login to the CMX Engage dashboard, even if the account is in use.
CMX Engage Runtime
The following enhancements are made to the CMX Engage Runtime:
Connect Button Support
For the captive portals with only “Feedback” and “Help” options enabled, now a Continue button will be available in the portal using which the captive portal user can proceed further to explore the portal. Previously, the repeat users could not access the internet if only Feedback and Help options were enabled.
Table 1 Resolved Issues in the CMX Engage 3.2.13
CMX Engage Dashboard
For Engagement Rule, the unicode characters in the SMS messages are not displayed properly to the customers.
In the Proximity Rules, warning messages for Live, Pause, and Delete actions are not clear and appropriate.
CMX Engage Runtime
Security concern exists as the “To” and “From” e-mail IDs in the feedback form are exposed on the client side.
Table 2 Open Issues in the CMX Engage 3.2.13
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.