Configuring Web Intelligence Reports for Geo-Analysis

To configure a Web Intelligence report block to display data for geo-analysis, one of the dimensions in the data set (on the back-end) must be in the point of interest (POI) format. A POI is a structure containing the following information fields:

● POI name (mandatory)

● POI location {latitude and longitude} (mandatory)

● POI image

● POI associated link

The POI image is an icon (usually provided as an image URL) that represents the point of interest on the geo- analysis. The POI associated link is a URL containing meta-information about the point of interest. These fields are optional and are not necessarily required to design the report as a geo-analysis.

An example of a valid table schema for a geo-analysis (based on the above data):

{<POI name>, <Latitude>, <Longitude>, <Image URL>, <><Dimension 1>, <Dimension 2>, <Dimension 3>, <Measure>}

Example: Configuring a report-part (vertical table)

Below is an example of a vertical table configured for geo-analysis in Web Intelligence:

In the table above:

● <Latitude>,< Longitude>, <Image Url> and <Link Url> are the fields defining a POI

Note

The latitude and longitude values of the points of interest (POIs) in geo-analysis should be numeric. They cannot have string values.

● Id, Name, City, Quarter are the dimensions

● Carbon Footprint is the measure

● map is the keyword

● lt(n) depicts the table column for latitude values for POIs ('n' is the column# which starts from 1)

● lo(n): depicts the table column for longitude values for POIs

● poi(n): depicts the table column for the POI name

● od(n): is the table column for Open Document URLs for each POI

Note

You need to define an OpenDocument URL for each POI in the report-block. When the user taps a point of interest in the geo-analysis, a report-part opens to display data related to the POI.

● imu(n): depicts the column with an image URL for the POI icon

Note

1. If the image URLs for POIs are not available in the back-end data, you can embed image- icons in the table column itself and replace imu(n) with imd(n) (depicting image data) in the block- name. 2. If an image URL or embedded image is not provided for the POIs, each POI is displayed as a bubble

with the following characteristics:

Alert condition: Configure the alert condition to set the color to each bubble based on the value of the selected measure. To enable alert condition in Geo analysis, use _ca1 at the end of the

mandatory report block name syntax. This condition is applicable if you only have measures with no dimension. For more information on how to set alert condition in your Web Intelligence document,

see Using alerters to highlight results at http://help.sap.com/businessobject/product_guides/ boexir31SP4/en/xi31_sp4_webi_rich_en.pdf

If the alert condition is not set, the default bubble color is dark-brown. However, if the measure column header in the vertical table has been set to a particular color, the bubbles appear in the same color in the geo-analysis. In the example above, the Sales revenue measure column header color has been set to red, so the bubble appears red.

The bubble size of each POI in the geo-analysis corresponds to its measure value.

Note

Geo-analysis recognizes only numeric measure values for POIs.

3. In the report-block name syntax, map_lt(n)_lo(n)_poi(n) is the mandatory part. Image and Open Document URL are optional, but we recommend including them to get the best view of the geo- analysis.

Defining the Open Document field in the report block

For every POI, the Open Document URL in the table can be defined in any one of the following format:

● Format 1: iDocID=<identifierValue>&sIDType=CUID&sType=wid&sReportName=<ReportName>&sRefresh=Y &sReportPart=<ReportPartName>&lsS[Name]="<value>" Example: iDocID=AdvPOc3AnzxOg85hQZhmTNA&sIDType=CUID&sType=wid&sReportName=Charts&sRefresh=Y &sReportPart=Margin&lsSCity="+[City]+" ● Format 2:<identifierValue>/<ReportName>/<ReportPartName> Example: AdvPOc3AnzxOg85hQZhmTNA/Charts/Margin ● Format 3: http://<servername>:<port>/BOE/OpenDocument/opendoc/openDocument.jsp? <parameter1>&<parameter2>&...&<parameterN> Example: http://10.53.141.252:8080/BOE/OpenDocument/opendoc/openDocument.jsp? iDocID=AdvPOc3AnzxOg85hQZhmTNA&sIDType=CUID&sType=wid&sReportName=Charts&sRefresh=Y &sReportPart=Margin&lsSCity="+[City]+"

Using formats 1 and 2, you can configure multiple Open Document URLs for each POI. Each URL should be separated by a '||'. Multiple OpenDoc URLs should be in the following format:

OpenDocURL1||OpenDocURL2||OpenDocURL3

In this case, the user can view multiple successive report-parts by swiping a finger on the pop-up (for a POI) on the device screen. The report-part corresponding to each OpenDocURL appears in the same sequence in the pop- up as set in the above syntax.

Using format 3, the document specified in the URL opens and behaves similarly to the default OpenDocument link. For more information about viewing documents using OpenDoc, see: http://help.sap.com/businessobject/ product_guides/boexir4/en/xi4_opendocument_en.pdf .

Note

1. If the Open Document URL for a POI is not defined in the valid format, the application ignores the URL value for the POI.

2. All the Open Document URLs configured for a POI (separated by '||' ) should be consistent in format. Each URL should include all the parameters as shown in the URL format above.

5

Managing Dashboards support for Android