To ease the connection between Cisco Spaces and Wireless network, and to do the required configurations in the wireless nerwork, Cisco Spaces now provides a new setup (Setup v2) flow. The new setup has provision to connect Cisco Spaces to Cisco AireOS or Cisco Meraki. Based on the wireless network you select, various methods through which you can connect to the particular network are displayed. When you select a particular method, the steps to connecting through that method is displayed along with the configuration instructions.

In the Cisco Spaces dashboard, when you choose Setup > Wireless Network, in the Connect your wireless Network window, a new button Add New is displayed. You can get the configuration instructions for a particular method using this button. For example, suppose you want to connect the Cisco Spaces to Cisco AireOS using a Cisco Spaces Connector. For that, click the Add New button, and click Select for Cisco AireOS/Catalyst. Then click Select for Via Spaces Connector. The Prerequisities for uisng this method is displayed. Click Customize Setup. Now a new bar Connect via Spaces Connector appears in the Connect your wireless network window. Click the drop arrow at the far right of the bar to view the configuration instructions for this method. The steps required for configuration such as Create a new token, Add Controllers, and Import Controllers , and so on will be available in the corresponding step at which they are required.

In the Cisco Spaces dashboard, the CMX Connector and Spaces Connector options are no more available directly under Setup. A new option Wireless Networks is added under Setup for configuring the connetors.

The Add New button in the Connect your wireless network window enables you to display the configuration instructions for Cisco Spaces Connector and CMX Tethering.

Once added, a bar correpsonding to the wireless network and method selected appears in the Connect your wireless Network window. For Cisco Spaces Connector, a bar Connect via Spaces Connector appears. You can create the token using Create a new token provided at Step 2 of the configuration instructions, and you can add wireless controllers using Add Controllers provided at Step 3. You can then import the wireless controllers using Import Controllers provided at Step 4.

For CMX Tethering, a bar Connect via CMX Tethering appears. You can create the token using Create New Token provided at Step 2, and after configuring the token in Cisco CMX, you can add the Cisco CMX node to the location hierarchy using Add CMX provided at Step 3.

The Behavior Metrics feature is enhanced to display performance on core metrics and the impacting factors separately. The report tabs now displayed are Behavior Metrics, WiFi Adoption, and Right Now. The Business Metrics tab is renamed as Behavior Metrics. The report tabs that were displayed at the far left of the window are now displayed at the top of the window. By default, now the Behavior Metrics report tab is shown.

The Behavior Metrics tab will now have the following sections:

Performance Benchmarking: Performance on Core Metrics relative to Peers

Visit Duration across locations, Visit Duration for key locations, Visit Duration for sub brands, Visit Duration Distribution along with Visit Frequency across locations, Visit Frequency for key locations, Visit Frequency for sub brands, and Visit Frequency Distribution are shown in this section.

Diagnostics: Factors that Impact or are Impacted by the Core Metrics

The graphs for Visit Duration by Visit Number, Repeat Visitors and Visit Recency across locations, Repeat Visitors and Visit Recency for key locations, and Repeat Visitors and Visit Recency for sub brands are shown in this section. In addition, Visit Distribution for Hour of day and Visit Distribution for day of week are displayed. Graphs showing the impact of store size on visits such as Size of Store and visit duration and Size of store and No. of Visits are also shown.

If the wireless network is Cisco Meraki , when you import a Meraki network location to Location Hierarchy, now the Notification URL automatically gets configured in Cisco Meraki. Previously, you had to manually configure the notification URL in Cisco Meraki for location updates.

Note	This support is not applicable for the Meraki networks added using Meraki API Key.