Introduction

CMaps Analytics Extension for Web Intelligence version 3, allows for embedded CMaps Analytics Designer views inside of Web Intelligence reports. Unlike older versions of this extension, this version uses HTML5 based map views and requires no other server software.

CMaps Analytics Extension V3 also uses Google Maps, unlike its predecessors which used SAP Dashboards with TomTom and MapBox. The end result is near identical through V3, includes some enhancements that dramatically simplify the workflow and configuration.

Need to install CMaps Analytics Extension?

View the install and admin guide

Result columns

• Object 1 Dimension [mandatory]
• Object 2 Dimension [optional]
• Objects 2/3 Measure [mandatory]
• Other Objects Any Type [Optional]

There are two different schemes for the initial dimensions in the results columns.

1) If there is only one dimension column before the first measure column then the values are taken as the labels for the points on the map and if the “Coordinate hint� property (see the Coordinate Hint column property section above) is not set then the value is also sent for geocoding to establish the location of the point on the map.

2) If there are two dimension columns before the first measure then the first one is the layer name (as specified in the CMaps designer, see “Configuration� property below) in which the point is to be plotted. The second dimension is the label for the point (see case 1 above for more details).

The first measure column and all subsequent columns (whether dimensions or measures) provide values for display in the info box which is associated with the point on the map.

Although it is possible to specify the order and meaning of columns inside the CMaps designer, this information is not used inside DecisionPoint, rather data is always passed into the map as defined in the two scenarios above.

Configuration

The configuration for a Centigon Maps component is provided through an XML file which is generated by the Centigon CMaps Designer. Refer to the CMaps documentation on how to create your map and export the XML configuration file. Once you have saved the configuration file to your local machine, click the “Pick XML File� button and open it in DecisionPoint.

Note: If you need to make changes to the configuration you can change it in the CMaps Designer, re-save it and then re-load it into DecisionPoint.

API Key

If you create your configuration file with the CMaps designer then it should have a valid API key embedded inside it. As a result you do not normally need to specify an API key inside DecisionPoint.

However, if you do need to add an API key to a configuration file (for example if you are using a generic map template configuration file) or you want to override the API key in a configuration file, then this property allows you to do so.

Visible Layers

The visible layers property allows you to specify which of the layers in the CMap are visible. It can take two forms: 1) The name of a single layer specified as a string 2) A list of layer names each specified as a string.

Examples that are valid:

Points

States

=list(“Points”,”States”)

=’Layer List’!selectedValues

Note: the names must exactly match the names of the layers as defined in the CMaps designer.

All Layers Visible by Default

If the value of “Visible Layers� is either an empty string or an empty list then either all or none of the layers are shown depending on the setting of this property

Visible Layers Controlled by Drill

This property overrides both of the previous two and drives the layer selection from the current level of drill in the CMaps component’s dataset. In order for this to work the names of the dimensions in the hierarchy must exactly match the names of the layers to be shown in the CMap configuration file.

For example if you have a hierarchy “Region� which consist of the dimensions Region, State and City, then the layers in the CMap must also be named Region, State and City