Custom Metrics and Reports

Transcription

1 Custom Metrics and Reports Release by Kony, Inc. All rights reserved 1 of 124

2 Custom Metrics and Reports Guide Copyright 2013 Kony, Inc. All rights reserved. July, 2015 This document contains information proprietary to Kony, Inc., is bound by the Kony license agreements and may not be used except in the context of understanding the use and methods of Kony Inc, software without prior, express, written permission. Kony, Empowering Everywhere, Kony MobileFabric, Kony Modeler,and Kony Visualizer are trademarks of Kony, Inc. Microsoft, the Microsoft logo, Internet Explorer, Windows, and Windows Vista are registered trademarks of Microsoft Corporation. Apple, the Apple logo, itunes, iphone, ipad, OS X, Objective-C, Safari, Apple Pay, Apple Watch and Xcode are trademarks or registered trademarks of Apple, Inc. Google, the Google logo, Android, and the Android logo are registered trademarks of Google, Inc. Chrome is a trademark of Google, Inc. BlackBerry, PlayBook, Research in Motion, and RIM are registered trademarks of BlackBerry. All other terms, trademarks, or service marks mentioned in this document have been capitalized and are to be considered the property of their respective owners by Kony, Inc. All rights reserved 2 of 124

3 Custom Metrics and Reports Guide Revision History Date Document Version Description of Modifications/Release 07/11/ Document updated for 6.5 release. 09/05/ Modified images in Custom Metrics section. 08/11/ Added Implementing Custom Metrics in Kony Server section and Custom Metrics APIs section. 05/23/ New document created for Kony Cloud - Custom Metrics and Custom Reports page by Kony, Inc. All rights reserved 3 of 124

4 Custom Metrics and Reports Guide Table of Contents 1. Custom Metrics Prerequisites Defining Custom Metrics in Kony Cloud Rules for Custom Metrics Data Types 9 2. Implementing Custom Metrics Implementing Custom Metrics in Kony Visualizer Implementing Custom Metrics in Kony Server Custom Metrics APIs for Kony Server com.konylabs.middleware.metrics.konycustommetricsdataset com.konylabs.middleware.metrics.konycustommetrics MetricsException Custom Reports Creating a Report (Table, Chart, and Crosstab) Saving Custom Reports and Ad Hoc Views Running Custom Reports Editing Ad Hoc Views Advanced Actions in Custom Reports by Kony, Inc. All rights reserved 4 of 124

5 1. Custom Metrics Custom Metrics and Reports Guide 1. Custom Metrics Custom metrics is a feature of Kony Development Cloud that enables an application developer to capture custom data from an application and build reports using the data. In addition to reports, the application developer also receives access to a set of standard metrics that are gathered from the application like the platform channel to use in building custom reports. This feature is available to any application deployed to an app services server in the development cloud. The cloud management portal enables a user to define custom metrics. Administrators and owners of the cloud account will see Custom Metrics and Custom Reports under Console tab: Custom Metrics - enables users to add or delete metrics that they intend to send from the application. The Custom Metrics page shows a list of development clouds (environments) in the account and a list of applications deployed in each cloud. If a user deploys an application to Kony Development Cloud, it appears in the Custom Metrics page. Custom Reports - enables users to create/modify/save reports with the metrics created in the custom metrics screen. A user can also choose to save reports as private reports (accessible only to the creator) or shared reports (accessible to all users who have permission to view custom reports in that account) by Kony, Inc. All rights reserved 5 of 124

6 1. Custom Metrics Custom Metrics and Reports Guide Note: The developer must register at manage.kony.com to access the Custom Metrics page. 1.1 Prerequisites Following are the prerequisites for creating custom metrics and generating custom reports in Kony Cloud: 1. A working account in Kony Cloud. 2. Active Kony Development Cloud. 3. An application deployed to Kony Development Cloud. 1.2 Defining Custom Metrics in Kony Cloud The Custom Metrics page allows an application developer to define the metrics for an application. Each metric is identified by a key that has to be unique within the application. There are six types of data: String, Boolean, Long (Integer), Double, Date, and Timestamp. The page shows all development clouds and applications deployed to these clouds. To add custom metric parameters for an application, under Custom Metrics tab in the Reports secction of the application, click on + Add Custom Metric button. For applications that already have custom metrics defined, clicking on Add + will show the list of Parameter Names, Data Type, and Default Aggregation function. The application can send multiple key-value pairs that will be stored as custom metrics for reporting purposes. The user must register each key sent by the application and provide the Data Type and Default Aggregation values by Kony, Inc. All rights reserved 6 of 124

7 1. Custom Metrics Custom Metrics and Reports Guide To create a custom metric, follow these steps: 1. Click Add Custom Metric. The following pane appears. 2. Enter a name in the Name (key) area. Each metric is identified by a key that must to be unique within the application. The application code must use the same Name for sending data in the key-value pairs in JSON string. The key is case insensitive by Kony, Inc. All rights reserved 7 of 124

8 1. Custom Metrics Custom Metrics and Reports Guide 3. Select a Data Type from the list. The available values are Long (integer values), Double (values with decimal points like 12.5), String, and Date. Note: The data type mentioned here must match the data type sent from the application for the metric name. 4. Select a Default Aggregation from the list. The Default Aggregation is the cumulative function you apply to the data while building the application. The available values are Sum, Average, Highest, Lowest, Count, and Distinct Count. Default Aggregation functions are only applicable for Long and Double. 5. Click Save. The parameters will be defined and saved under the application name. The custom metrics defined will be sent to the application to collect data. 6. Click Cancel to cancel adding custom metrics to the application. For example, the image below shows custom metrics for one of our sample apps KonyStore: To delete a custom metric, follow these steps: 2015 by Kony, Inc. All rights reserved 8 of 124

9 1. Custom Metrics Custom Metrics and Reports Guide 1. Select the custom metric in the application. 2. Click Delete. A warning message appears. 3. Click Yes, I'm sure to delete the custom metric. Note: Data from an application with a key corresponding to a deleted parameter name will not be saved. Existing reports and ad hoc views already created from the domain that use the deleted parameter will work. However, creating new ad hoc views from the same domain will have the underscore _ deleted suffix for the parameter name to denote to the developer building reports that this is currently a deleted parameter. 1.3 Rules for Custom Metrics Data Types Long - Integer values Double - Values with decimal point like Boolean - true/false String - Any string value, maximum length 500 characters. Date - String value denoting date in the format yyyy-mm-dd. Example: " " 2015 by Kony, Inc. All rights reserved 9 of 124

10 1. Custom Metrics Custom Metrics and Reports Guide Timestamp - String value denoting timestamp. Valid formats for timestamp are shown below o yyyy-mm-dd hh:mm:ss --- preferred format o yyyy-mm-dd hh:mm:ssz o yyyy-mm-dd hh:mm:ss+hh:mm o yyyy-mm-dd hh:mm:ss-hh:mm o z stands for zulu (UTC) o +hh:mm is positive offset of time from UTC o -hh:mm is negative offset from UTC. o Example: " :02:55" " :02:55z" " :02:55+05:30" " :02:55-05:30" 2015 by Kony, Inc. All rights reserved 10 of 124

11 2. Implementing Custom Metrics Custom Metrics and Reports Guide 2. Implementing Custom Metrics Custom metrics can be implemented through code on Client side as well as the Server side. Custom metrics support Kony Studio and MBAAS SDK clients. The Data Type that is defined in cloud portal for the application must match the data type sent from the application. After the data is defined, you can use this data to build reports. 2.1 Implementing Custom Metrics in Kony Visualizer To implement custom metrics in Kony Studio, you should send data from your application to the custom metrics in Kony Cloud. You can send custom metrics by calling a new API in Kony Studio, KNYMetricsService.sendCustomMetrics (<formname>,<json string>). The Data Type that is defined in the KonyCloud portal for the application must match the data type sent from the application. After the data are defined, you can use the data to build reports. The new API will initiate a service callback to Kony Server in a development cloud with service ID as capturekonycustommetrics. To define metrics in Kony Studio, follow these steps: 1. In Kony Studio, design a form for an application. 2. To implement the metrics for an application in Kony Studio, choose one of the following methods: a. Right-click on a form element. Define the metrics using KNYMetricsService.sendCustomMetrics in an onclick event by adding a code snippet to the Action Sequence. b. Configure the metrics in a code module by Kony, Inc. All rights reserved 11 of 124

12 2. Implementing Custom Metrics Custom Metrics and Reports Guide 3. Define the metrics. See the example below. a. Following are the supported formats for key values: Each JSON object in the below formats correspond to one set of associated data. 1) Array of JSON Objects with single key: [ { "met1": "metval1" }, { "met2": "metval2" } ] Use this format if data is not associated. For example, met1 and met2 are unassociated data points. 2) JSON Array with single JSON object with multiple keys: [ { "met1": "metval1", "met2": "metval2" } ] Use this format for sending a single set of associated data. For example, in the report you can check value of met2 when met1 value is metval1. 3) JSON array with multiple JSON objects: [ { "met1": "metval1", "met2": "metval2" 2015 by Kony, Inc. All rights reserved 12 of 124

13 2. Implementing Custom Metrics Custom Metrics and Reports Guide }, { "met1": "metval3", "met2": "metval4" } ] Preferred format for sending data to collect data and multiple sets of associated data. The following example shows a custom metrics code defined for an element in Kony Studio. var custmetrics = [{"onsale":true,"prodname":"ipad 16 GB","prodPrice":450.0,"salePrice":400.0,"prodSKU":"1231sdf2","r ating":4.5}] KNYMetricsService.sendCustomMetrics("frmProduct", custmetrics) For more information on metrics APIs, refer SDK documentation. 4. After you define the Custom Metrics in Kony Studio, rebuild and publish the application to the same cloud for which the custom metrics was defined. 5. After the application is published and the appropriate trigger point is hit (button click or form load wherever the above API is called), metrics will be sent to cloud and stored for reporting purposes. Note: It takes about minutes after the data is sent from an application for the data to be reflected on cloud reports. 2.2 Implementing Custom Metrics in Kony Server Important: Familiarize yourself with Custom metrics APIs at Custom Metrics APIs before you proceed with this section by Kony, Inc. All rights reserved 13 of 124

14 2. Implementing Custom Metrics Custom Metrics and Reports Guide You can implement Custom Metrics in Kony Server using java classes defined for the application such as preprocessor, postprocessor class for services or java service class. Using class allows you to easily add/edit custom metrics from the server code without affecting the client logic. Pre-requisites: Metrics defined for the application in the management console. Java programming knowledge. To implement metrics in Kony Server, follow these steps: 1. In Kony Studio, navigate to and open the service you want to set metrics for. 2. Do one of the following i. If your preprocessor and/or post processor class exists, define the logic for sending custom metrics in them. ii. If you do not have preprocessor and post processor classes, create them with custom metrics logic. See examples below. Preprocessor example package com.kony.preprocessors; import java.util.date; import java.util.hashmap; import org.apache.log4j.logger; import com.konylabs.middleware.common.datapreprocessor; import com.konylabs.middleware.common.mwconstants; 2015 by Kony, Inc. All rights reserved 14 of 124

15 2. Implementing Custom Metrics Custom Metrics and Reports Guide import com.konylabs.middleware.controller.datacontrollerrequest; import com.konylabs.middleware.dataobject.result; import com.konylabs.middleware.metrics.konycustommetrics; import com.konylabs.middleware.metrics.konycustommetricsdataset; public class CustomMetricsPreProcessor1 implements DataPreProcessor{ Logger logger = Logger.getLogger public boolean execute(hashmap map, DataControllerRequest request, Result result) throws Exception { KonyCustomMetrics kmetrics = new KonyCustomMetrics(); KonyCustomMetricsDataSet metricsdataset = new KonyCustomMetricsDataSet(); metricsdataset.setmetricsstring("product Name", "Dell Vostro"); metricsdataset.setmetricsboolean("on Sale", true); metricsdataset.setmetricslong("product ID", ); metricsdataset.setmetricsdouble("product Price", ); Date now = new Date(); 2015 by Kony, Inc. All rights reserved 15 of 124

16 2. Implementing Custom Metrics Custom Metrics and Reports Guide metricsdataset.setmetricsdate("on Sale Date", now); metricsdataset.setmetricstimestamp("promo start time", " ", "yyyy-mm-dd"); metricsdataset.setmetricstimestamp("promo end time", " :00:00"); KonyCustomMetricsDataSet metricsdataset1 = new KonyCustomMetricsDataSet(); metricsdataset.setmetricsstring("product Name", "Lennovo Lattitude"); metricsdataset.setmetricsboolean("on Sale", true); metricsdataset.setmetricslong("product ID", ); metricsdataset.setmetricsdouble("product Price", ); metricsdataset.setmetricsdate("on Sale Date", now); kmetrics.addcustommetrics(metricsdataset); kmetrics.addcustommetrics(metricsdataset1); request.setattribute(mwconstants.c_custom_metrics, kmetrics); return true; } } Postprocessor example 2015 by Kony, Inc. All rights reserved 16 of 124

17 2. Implementing Custom Metrics Custom Metrics and Reports Guide package com.kony.postprocessors; import java.util.list; import org.apache.log4j.logger; import com.konylabs.middleware.common.datapostprocessor; import com.konylabs.middleware.common.mwconstants; import com.konylabs.middleware.controller.datacontrollerrequest; import com.konylabs.middleware.dataobject.result; import com.konylabs.middleware.metrics.konycustommetrics; import com.konylabs.middleware.metrics.konycustommetricsdataset; public class CloudPostProcessor implements DataPostProcessor { private static final Logger LOG = Logger.getLogger public Object execute(result arg0, DataControllerRequest arg1) throws Exception { // TODO Auto-generated method stub if (null!= arg1.getattribute(mwconstants.c_custom_metrics)) { KonyCustomMetrics objkonycustommetrics = (KonyCustomMetrics) arg1.getattribute(mwconstants.c_custom_metrics); 2015 by Kony, Inc. All rights reserved 17 of 124

18 2. Implementing Custom Metrics Custom Metrics and Reports Guide String metricsjson = objkonycustommetrics.getcustommetricsjson (); LOG.debug("::KONY METRICS JSON IN POST PROCESSOR BEFORE MODIFICATIONS== " + metricsjson); List<KonyCustomMetricsDataSet> cusmetdatasetlist = objkonycustommetrics.getcustommetrics(); LOG.debug(":::::: LIST SIZE BEFORE CLEAR:::::" + cusmetdatasetlist.size()); objkonycustommetrics.clearcustommetrics(); LOG.debug(":::::: LIST SIZE AFTER CLEAR:::::" + cusmetdatasetlist.size()); if (cusmetdatasetlist.size() > 0) { KonyCustomMetricsDataSet objkonycustommetricsdataset = (KonyCustomMetricsDataSet)cusMetDataSetList.get(0); cusmetdatasetlist.remove(0); String key1value = objkonycustommetricsdataset.get("product Name").toString(); LOG.debug("::KONY METRICS GET METHOD== " + Dell Vostro); objkonycustommetricsdataset.remove("promo end time"); objkonycustommetricsdataset.remove("product Name"); objkonycustommetricsdataset.setmetricsstring("product Name", "modified value"); 2015 by Kony, Inc. All rights reserved 18 of 124

19 2. Implementing Custom Metrics Custom Metrics and Reports Guide cusmetdatasetlist.add(0, objkonycustommetricsdataset); } for (KonyCustomMetricsDataSet dataset : cusmetdatasetlist) { objkonycustommetrics.addcustommetrics(dataset); } LOG.debug(":::::: FINAL CUSTOM METRICS LIST :::::" + objkonycustommetrics.getcustommetrics()); arg1.setattribute(mwconstants.c_custom_metrics, objkonycustommetrics); } return arg0; } } Note: If preprocesser and postprocessor class were created now, enter those details in their respective text boxes. 3. Right-click your service and select Build a Jar. The created jar file should be in /services/ <your service> (xml or json or java)/lib 4. Right-click on your project and select Properties. Application Properties window is displayed. 5. In Kony Server Details tab, make sure that the jar you created is available under App Libraries section. 6. Right-click the project and select Build all to build and publish the application. Full publish the project to deploy jar file by Kony, Inc. All rights reserved 19 of 124

20 2. Implementing Custom Metrics Custom Metrics and Reports Guide The application is published and ready to provide custom metrics when an appropriate service is invoked by Kony, Inc. All rights reserved 20 of 124

21 3. Custom Metrics APIs for Kony Server Custom Metrics and Reports Guide 3. Custom Metrics APIs for Kony Server The following section contains Javadoc information about classes. These class define the API required for sending custom metrics from Kony Server. 3.1 com.konylabs.middleware.metrics.konycustommetricsdataset The com.konylabs.middleware.metrics.konycustommetricsdataset class contains methods required for setting custom metrics. To enable custom metrics from server, the following methods are available. setmetricsstring setmetricsboolean setmetricslong setmetricsdouble setmetricsdate setmetricsdate setmetricsdate setmetricstimestamp setmetricstimestamp getmetricsmap get remove tostring setmetricsstring This method is used to set custom metrics for data type string by Kony, Inc. All rights reserved 21 of 124

22 3. Custom Metrics APIs for Kony Server Custom Metrics and Reports Guide Signature public void setmetricsstrting(string key,string value) throws MetricsException Input Parameters key value Return Values Void. Can throw metricsexception Java Example metricsdataset.setmetricsstring("product Name", "Dell Vostro"); setmetricsboolean This method is used to set custom metric for data type boolean. This method takes true or false as values Signature public void setmetricsboolean(string key,boolean value) Input Parameters key value Return Values Void 2015 by Kony, Inc. All rights reserved 22 of 124

23 3. Custom Metrics APIs for Kony Server Custom Metrics and Reports Guide Java Example metricsdataset.setmetricsboolean("on Sale", true); setmetricslong This method is used to set custom metric for data type long Signature public void setmetricslong(string key,long value) Input Parameters key value Return Values Void Java Example metricsdataset.setmetricslong("product ID", ); setmetricsdouble This method is used to set custom metric for data type double Signature public void setmetricsdouble(string key,double value) Input Parameters: key value 2015 by Kony, Inc. All rights reserved 23 of 124

24 3. Custom Metrics APIs for Kony Server Custom Metrics and Reports Guide Return Values Void Java Example metricsdataset.setmetricsdouble("product Price", ); setmetricsdate This method is used to set custom metric for data type date. Input value for this method is Date Object and the format should be 'yyyy-mm-dd' Signature public void setmetricsdate(string key,date date) throws MetricsException Input Parameters: key - - String value - - Date Return Values Void. Can throw metricsexception Java Example metricsdataset.setmetricsdate("on Sale Date", " "); 2015 by Kony, Inc. All rights reserved 24 of 124

25 3. Custom Metrics APIs for Kony Server Custom Metrics and Reports Guide setmetricsdate This method is used to set custom metric for data type date. The input takes date value as a string and the date value format should be 'yyyy-mm-dd' Signature public void setmetricsdate(string key,string val) throws MetricsException Input Parameters key - - String value - - String, Date value in string Return Values Void. Can throw metricsexception Java Example metricsdataset.setmetricsdate("on Sale Date", " "); setmetricsdate This method is used for setting custom metric for data type date. This method takes date and format as a string and evaluates the date value with the given format. Input takes date value as a string and the date value format should be 'yyyy-mm-dd' Signature public void setmetricsdate(string key,string datestr,string format) throws MetricsException 2015 by Kony, Inc. All rights reserved 25 of 124

26 3. Custom Metrics APIs for Kony Server Custom Metrics and Reports Guide Input Parameters: key - - key value - - date as string format - - date pattern timezone - - optional parameter Return Values Void. Can throw metricsexception Java Example metricsdataset.setmetricsdate("on Sale Date", " ", "yyyy-mmdd"); setmetricstimestamp This method is used to set custom metric for data type timestamp. This method takes value as a string and evaluates with any one of the following formats: yyyy-mm-dd hh:mm:ss yyyy-mm-dd hh:mm:ssz yyyy-mm-dd hh:mm:ss+hh:mm yyyy-mm-dd hh:mm:ss-hh:mm <ts>- timestamp in UTC. Timestamp value. <ts>z - timestamp in UTC. Timestamp in above format + lower case z by Kony, Inc. All rights reserved 26 of 124

27 3. Custom Metrics APIs for Kony Server Custom Metrics and Reports Guide <ts>+hh:mm - timestamp in UTC + positive offset in hours and minutes, separated by colon. <ts>-hh:mm -timestamp in UTC + negative offset in hours and minutes separated by colon. Please note that <ts> = yyyy-mm-dd hh:mm:ss For example, " :02:55" " :02:55z" " :02:55+05:30" " :02:55-05:30" Signature public void setmetricstimestamp(string key,string value) throws MetricsException Input Parameters: key value Return Values Void. Can throw metricsexception Java Example metricsdataset.setmetricstimestamp("promo start time", " :00:00", "yyyy-mm-dd"); 2015 by Kony, Inc. All rights reserved 27 of 124

28 3. Custom Metrics APIs for Kony Server Custom Metrics and Reports Guide setmetricstimestamp This method is used to set custom metric for data type timestamp. This method takes value as a string and evaluates with any one of the following time stamp patterns: yyyy-mm-dd hh:mm:ss yyyy-mm-dd hh:mm:ssz yyyy-mm-dd hh:mm:ss+hh:mm yyyy-mm-dd hh:mm:ss-hh:mm Signature public void setmetricstimestamp(string key,string value,string pattern) throws MetricsException Input Parameters: key value pattern Return Values Void. Can throw metricsexception Java Example metricsdataset.setmetricstimestamp("promo end time", " :00:00"); 2015 by Kony, Inc. All rights reserved 28 of 124

29 3. Custom Metrics APIs for Kony Server Custom Metrics and Reports Guide getmetricsmap This method returns custom metrics as a Hashmap Signature protected Map<String,Object> getmetricsmap() Input Parameters: None Return Values Map get This method retrieves value with the key in the current request scope Signature public Object get(string key) Input Parameters: key Return Values If the key exists, returns value as an object. If the key does not exist, returns null Remove This method removes key and value from metrics in the current request scope by Kony, Inc. All rights reserved 29 of 124

30 3. Custom Metrics APIs for Kony Server Custom Metrics and Reports Guide Signature public boolean remove(string key) Input Parameters: key Return Values True if successfully removed, otherwise returns false tostring This method retrieves entire custom metrics as a json string Signature public String tostring() Overrides: tostring in class Object Return Values None 3.2 com.konylabs.middleware.metrics.konycustommetrics This class contains methods to add and get custommetrics. These methods can be added to Preprocessor and PostProcessor class by the App developer to send custom metrics. Custom metrics is converted into a JSON string before sending it to the back end for processing. The com.konylabs.middleware.metrics.konycustommetrics class has the following methods: 2015 by Kony, Inc. All rights reserved 30 of 124

31 3. Custom Metrics APIs for Kony Server Custom Metrics and Reports Guide addcustommetrics getcustommetrics getcustommetricsjson clearcustommetrics addcustommetrics This method takes KonyCustomMetricsDataSet object and adds as a json string Signature public void addcustommetrics(konycustommetricsdataset metricsdataset) Input Parameters metricsdataset Return Values None getcustommetrics This method returns all KonyCustomMetricsDataSet objects that were added using addcustommetrics method Signature public List<KonyCustomMetricsDataSet> getcustommetrics() throws MetricsException Input Parameters None 2015 by Kony, Inc. All rights reserved 31 of 124

32 3. Custom Metrics APIs for Kony Server Custom Metrics and Reports Guide Return Values Void. Can throw metricsexception getcustommetricsjson This method returns custom metrics as a JSONArray string Signature public String getcustommetricsjson() Input Parameters None Return Values String clearcustommetrics This method clears all custom metrics in the current request scope Signature public boolean clearcustommetrics() Input Parameters None Return Values None 2015 by Kony, Inc. All rights reserved 32 of 124

33 3. Custom Metrics APIs for Kony Server Custom Metrics and Reports Guide 3.3 MetricsException MetricsException is a class that occurs if an exception takes place while processing metrics data. Following are various validation scenarios. metrics_dateparse_error=the date string you provided does not match the format provided value as <format>. Unable to parse date metrics_ts_error=the timestamp string you provided does not match the default format of yyyy-mm-dd hh:mm:ss, yyyy-mm-dd hh:mm:ssz, yyyy-mmdd hh:mm:ss+hh:mm, or yyyy-mm-dd hh:mm:ss-hh:mm. Unable to parse timestamp metrics_tsparse_error=the timestamp string you provided does not match the format provided value as <format>. Unable to parse timestamp metrics_notnull_error=could not be added to custom metrics as null is not a valid value. metrics_date_null_error=the date/timestamp value cannot be null metrics_error=please pass the valid value 2015 by Kony, Inc. All rights reserved 33 of 124

34 4. Custom Reports After you have defined the custom metrics for your application, you can create a custom report. A custom report can be generated in three formats: table, report, and crosstab. Table Chart 2015 by Kony, Inc. All rights reserved 34 of 124

35 Crossta b Click the following links to view the user interface elements of these reports. 1. Table 2. Chart 3. Crosstab Note: You must be an owner or an administrator to create reports. 4.1 Creating a Report (Table, Chart, and Crosstab) To create a custom report, follow these steps: 1. Click Create Report in Kony Cloud. The following Data Chooser: Source dialog appears. JasperReports Server 5.6 JasperReports Server by Kony, Inc. All rights reserved 35 of 124

36 2. Expand Domains folder and select your domain. A domain represents a data set for which the user has defined custom metrics. The Domains folder shows domains for all applications in an account. a. There are two types of domains. Standard Metrics is the generic domain. It contains metrics collected for all applications deployed to development clouds in the cloud account. The Standard Metrics domain is available even if no custom metrics have been defined. This enables a user to build custom reports with the generic metrics that are captured for all their development clouds. The parameters captured are: i. Application Name ii. Application Type iii. Channel iv. Device Model 2015 by Kony, Inc. All rights reserved 36 of 124

37 v. Form ID vi. OS Version vii. Platform viii. Service ID ix. Timestamp_UTC -Timestamp of request in UTC x. Timestamp_Local -Timestamp when the service request was received in the timestamp set in a user's profile in manage cloud portal xi. ity, Country, Region, ZIP Code - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. xii. Internal Duration - Time spent by the service call in Kony App Services for internal processing xiii. External Duration - Time spent by the service call in Kony App Services for external call from Kony Server to backend xiv. PostProcessor Duration - Time spent by the service call in Kony app services in custom post-processing logic in the service xv. PreProcessor Duration - Time spent by the service call in Kony app services in custom pre-processing logic in the service xvi. Parse Duration - Time spent by the service call in Kony app services in parsing response from external source xvii. Total Duration - Total time spent in Kony app services server for the service call, from the time request was received by the server until the response was sent back to device. Total duration is equal to the sum of all the duration fields. The parameters Standard Metrics and Events are: Fields 2015 by Kony, Inc. All rights reserved 37 of 124

38 1. Application Name - Name of the application 2. App Type - Type of the application. For example, Native, SPA 3. Channel - Channel of application. For example, Mobile, Tablet 4. Platform - Application platform. For example, ios, Android 5. Device Model - Model of client device. 6. Kony User ID - User ID of the end user using app. Value has to be set using the setuserid API in the application. 7. DeviceID - Unique ID of the device for the application. 8. User Agent - User agent of the client device from network call 9. OS Version - Version of the client device's OS. 10. Service Group - Integration service name of the service request for applications defined from MobileFabric console. 11. Service ID - This param denotes operation name of the integration/orchestration service request for MobileFabric console defined apps. ServiceID of the service for apps where servicedefinition is defined from Kony Visualizer Enterprise. 12. City - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 13. Country - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 14. Region - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 15. Zip Code - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 16. Event Application Name - Name of the application from Events data by Kony, Inc. All rights reserved 38 of 124

39 17. Event App Type - Type of the application. For example, Native, SPA 18. Event Channel - Channel of application. For example, Mobile, Tablet 19. Event Platform - Application platform. For example, ios, Android 20. Event Device Model - Model of client device. 21. Event Kony User ID - User ID of the end user using app. Value has to be set using the setuserid API in the application. 22. Event DeviceID - Unique ID of the device for the application. 23. Event User Agent - User agent of the client device from network call 24. Event Application Version - Version of the client application 25. Plugin Version IDE - Plugin versions of Kony Visualizer Enterprise used for building the app. This will be populated only for Crash event type. 26. Plugin Version Platform - Plugin version of platform (like ios plugin) used for building the app. This will be populated only for Crash event type. 27. SDK Type - If app is built using Kony mobile fabric SDK this will indicate type of SDK like ios, PhoneGap. 28. SDK Version - Version of the mobile fabric SDK used in the client binary. 29. Event Type - Type of the application event. ex: FormEntry, Gesture 30. Event Sub Type - Event sub type of the application event. Meaning of subtype depends on the event type. For FormEntry event subtype denotes form entered. For Gesture it denotes type of Gesture like doubleclick. 31. Event Form ID - Form ID of the form where the application event occurred. 32. Event Widget ID - Widget Id of the widget where the application event was triggered. Not applicable for events that do not involve a widget like FormEntry, FormExit by Kony, Inc. All rights reserved 39 of 124

40 33. Event Flow Tag - Optional parameter that can be set by developer via an API call to identify a flow. Helps in easy identification for data analysis. 34. Error Code - Error code if the event type is error and Exception code if event type is exception. 35. Error message Error message. 36. Error Crash Report Crash Report from the device for event type Crash. Data is not symbolicated. 37. Custom Error Message Contains any custom message that is added by platform code or app developer to provide more info on error events. 38. Error File Application code file where error occurred. Applicable for event types Error/Exception if the same is available for type of error/exception. 39. Error Method Application function call where error occurred. Applicable for event types Error/Exception if the same is available for type of error/exception. 40. Error Stack Trace Stack trace of error. Applicable for event types Error/Crash if the same is available for type of error/crash. 41. Error Type Type of error. Ex: Error, Exception, Crash 42. Is Error true if the event type is error/crash and false if event type is exception. Not applicable for other event types. 43. Response Status Code Output status of the service response from the MobileFabric server 44. Events Meta Data Any meta data sent as part of the events data. Typically this is applicable for event type error, exception, crash, and custom. 45. Event TimeStamp_UTC Time stamp of event in UTC 46. Event TimeStamp_Local Time stamp of event in local time zone. Local time zone is set in user s profile in MobileFabric console by Kony, Inc. All rights reserved 40 of 124

41 47. Session TimeStamp_UTC Time stamp of session init in UTC 48. Session TimeStamp_Local Time stamp of session init in local time zone. Local time zone is set in user s profile in MobileFabric console. 49. Request TimeStamp_UTC Time stamp of service request in UTC 50. Request TimeStamp_Local Time stamp of service request in local time zone. Local time zone is set in user s profile in MobileFabric console. 51. Request MobileFabric app guid application guid generated on creation of an app in MobileFabric console. 52. Request MobileFabric app name application name provided on creation of an app in MobileFabric console. 53. Session MobileFabric app guid application guid generated on creation of an app in MobileFabric console. 54. Session MobileFabric app guid application name provided on creation of an app in MobileFabric console. 55. Object method Type of the object method ex. PUT, POST. Applicable for services with object mapping. 56. Object name Name of the object that is mapped in service request. Applicable for services with object mapping. 57. Integration service version header Version of the integration service requested by application in the service request header. 58. Integration service version Version of the integration service served by the application server for a service request. Measures: 1. Internal Duration - Time spent by the service call in Kony App Services for internal processing 2015 by Kony, Inc. All rights reserved 41 of 124

42 2. External Duration - Time spent by the service call in Kony App Services for external call from Kony Server to backend 3. PostProcessor Duration - Time spent by the service call in Kony app services in custom post-processing logic in the service 4. PreProcessor Duration - Time spent by the service call in Kony app services in custom pre-processing logic in the service 5. Parse Duration - Time spent by the service call in Kony app services in parsing response from external source 6. Total Duration - Total time spent in Kony app services server for the service call, from the time request was received by the server until the response was sent back to device. Total duration is equal to the sum of all the duration fields. 7. Error Line Line number in application code file where error occurred. Applicable for event types error/exception. 8. HTTP Response Code HTTP code of the service response obtained by the device. 9. Response Time Response time as viewed by the client device. That is time since service request is sent from device to server and response obtained back in the device. 10. Event Session Key Unique session identifier for the session in which the application event occurred. 11. Middleware Session Key Unique session identifier for application session data from session init call. 12. Object mapping duration (request) Time taken to map the object detail into service request by Kony app services. 13. Object mapping duration (response) Time taken to map the object detail into service response by Kony app services by Kony, Inc. All rights reserved 42 of 124

43 14. Count Sample custom field created to show count of application. This is to function as a count(*) for application session and service request calls. Note: Similar data is sometimes made available for different types of data like Events, Session, Service Requests, Error as data is stored in different tables for them and having different fields called out enables a more optimized query to run if only one type of network call is used in a custom report. Note: All duration fields indicate time duration in milli seconds. b. The domain has data of all service calls made to this application and all custom metrics that were sent. Note: To view only Custom Metrics service-related data for an application, add a prefilter or filter while creating reports for Service ID equals "capturekonycustommetrics." 3. Expand Domains folder and select your domain. A domain represents a data set for which the user has defined custom metrics. The Domains folder shows domains for all applications in an account. a. There are two types of domains. Standard Metrics is the generic domain. It contains metrics collected for all applications deployed to development clouds in the cloud account. The Standard Metrics domain is available even if no custom metrics have been defined. This enables a user to build custom reports with the generic metrics that are captured for all their development clouds. The parameters captured are: i. Application Name ii. Application Type iii. Channel iv. Device Model 2015 by Kony, Inc. All rights reserved 43 of 124

44 v. Form ID vi. OS Version vii. Platform viii. Service ID ix. Timestamp_UTC -Timestamp of request in UTC x. Timestamp_Local -Timestamp when the service request was received in the timestamp set in a user's profile in manage cloud portal xi. ity, Country, Region, ZIP Code - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. xii. Internal Duration - Time spent by the service call in Kony App Services for internal processing xiii. External Duration - Time spent by the service call in Kony App Services for external call from Kony Server to backend xiv. PostProcessor Duration - Time spent by the service call in Kony app services in custom post-processing logic in the service xv. PreProcessor Duration - Time spent by the service call in Kony app services in custom pre-processing logic in the service xvi. Parse Duration - Time spent by the service call in Kony app services in parsing response from external source xvii. Total Duration - Total time spent in Kony app services server for the service call, from the time request was received by the server until the response was sent back to device. Total duration is equal to the sum of all the duration fields. The parameters Standard Metrics and Events are: Fields 2015 by Kony, Inc. All rights reserved 44 of 124

45 1. Application Name - Name of the application 2. App Type - Type of the application. For example, Native, SPA 3. Channel - Channel of application. For example, Mobile, Tablet 4. Platform - Application platform. For example, ios, Android 5. Device Model - Model of client device. 6. Kony User ID - User ID of the end user using app. Value has to be set using the setuserid API in the application. 7. DeviceID - Unique ID of the device for the application. 8. User Agent - User agent of the client device from network call 9. OS Version - Version of the client device's OS. 10. Service Group - Integration service name of the service request for applications defined from MobileFabric console. 11. Service ID - This param denotes operation name of the integration/orchestration service request for MobileFabric console defined apps. ServiceID of the service for apps where servicedefinition is defined from Kony Visualizer Enterprise. 12. City - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 13. Country - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 14. Region - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 15. Zip Code - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 16. Event Application Name - Name of the application from Events data by Kony, Inc. All rights reserved 45 of 124

46 17. Event App Type - Type of the application. For example, Native, SPA 18. Event Channel - Channel of application. For example, Mobile, Tablet 19. Event Platform - Application platform. For example, ios, Android 20. Event Device Model - Model of client device. 21. Event Kony User ID - User ID of the end user using app. Value has to be set using the setuserid API in the application. 22. Event DeviceID - Unique ID of the device for the application. 23. Event User Agent - User agent of the client device from network call 24. Event Application Version - Version of the client application 25. Plugin Version IDE - Plugin versions of Kony Visualizer Enterprise used for building the app. This will be populated only for Crash event type. 26. Plugin Version Platform - Plugin version of platform (like ios plugin) used for building the app. This will be populated only for Crash event type. 27. SDK Type - If app is built using Kony mobile fabric SDK this will indicate type of SDK like ios, PhoneGap. 28. SDK Version - Version of the mobile fabric SDK used in the client binary. 29. Event Type - Type of the application event. ex: FormEntry, Gesture 30. Event Sub Type - Event sub type of the application event. Meaning of subtype depends on the event type. For FormEntry event subtype denotes form entered. For Gesture it denotes type of Gesture like doubleclick. 31. Event Form ID - Form ID of the form where the application event occurred. 32. Event Widget ID - Widget Id of the widget where the application event was triggered. Not applicable for events that do not involve a widget like FormEntry, FormExit by Kony, Inc. All rights reserved 46 of 124

47 33. Event Flow Tag - Optional parameter that can be set by developer via an API call to identify a flow. Helps in easy identification for data analysis. 34. Error Code - Error code if the event type is error and Exception code if event type is exception. 35. Error message Error message. 36. Error Crash Report Crash Report from the device for event type Crash. Data is not symbolicated. 37. Custom Error Message Contains any custom message that is added by platform code or app developer to provide more info on error events. 38. Error File Application code file where error occurred. Applicable for event types Error/Exception if the same is available for type of error/exception. 39. Error Method Application function call where error occurred. Applicable for event types Error/Exception if the same is available for type of error/exception. 40. Error Stack Trace Stack trace of error. Applicable for event types Error/Crash if the same is available for type of error/crash. 41. Error Type Type of error. Ex: Error, Exception, Crash 42. Is Error true if the event type is error/crash and false if event type is exception. Not applicable for other event types. 43. Response Status Code Output status of the service response from the MobileFabric server 44. Events Meta Data Any meta data sent as part of the events data. Typically this is applicable for event type error, exception, crash, and custom. 45. Event TimeStamp_UTC Time stamp of event in UTC 46. Event TimeStamp_Local Time stamp of event in local time zone. Local time zone is set in user s profile in MobileFabric console by Kony, Inc. All rights reserved 47 of 124

48 47. Session TimeStamp_UTC Time stamp of session init in UTC 48. Session TimeStamp_Local Time stamp of session init in local time zone. Local time zone is set in user s profile in MobileFabric console. 49. Request TimeStamp_UTC Time stamp of service request in UTC 50. Request TimeStamp_Local Time stamp of service request in local time zone. Local time zone is set in user s profile in MobileFabric console. 51. Request MobileFabric app guid application guid generated on creation of an app in MobileFabric console. 52. Request MobileFabric app name application name provided on creation of an app in MobileFabric console. 53. Session MobileFabric app guid application guid generated on creation of an app in MobileFabric console. 54. Session MobileFabric app guid application name provided on creation of an app in MobileFabric console. 55. Object method Type of the object method ex. PUT, POST. Applicable for services with object mapping. 56. Object name Name of the object that is mapped in service request. Applicable for services with object mapping. 57. Integration service version header Version of the integration service requested by application in the service request header. 58. Integration service version Version of the integration service served by the application server for a service request. Measures: 1. Internal Duration - Time spent by the service call in Kony App Services for internal processing 2015 by Kony, Inc. All rights reserved 48 of 124

49 2. External Duration - Time spent by the service call in Kony App Services for external call from Kony Server to backend 3. PostProcessor Duration - Time spent by the service call in Kony app services in custom post-processing logic in the service 4. PreProcessor Duration - Time spent by the service call in Kony app services in custom pre-processing logic in the service 5. Parse Duration - Time spent by the service call in Kony app services in parsing response from external source 6. Total Duration - Total time spent in Kony app services server for the service call, from the time request was received by the server until the response was sent back to device. Total duration is equal to the sum of all the duration fields. 7. Error Line Line number in application code file where error occurred. Applicable for event types error/exception. 8. HTTP Response Code HTTP code of the service response obtained by the device. 9. Response Time Response time as viewed by the client device. That is time since service request is sent from device to server and response obtained back in the device. 10. Event Session Key Unique session identifier for the session in which the application event occurred. 11. Middleware Session Key Unique session identifier for application session data from session init call. 12. Object mapping duration (request) Time taken to map the object detail into service request by Kony app services. 13. Object mapping duration (response) Time taken to map the object detail into service response by Kony app services by Kony, Inc. All rights reserved 49 of 124

50 14. Count Sample custom field created to show count of application. This is to function as a count(*) for application session and service request calls. Note: Similar data is sometimes made available for different types of data like Events, Session, Service Requests, Error as data is stored in different tables for them and having different fields called out enables a more optimized query to run if only one type of network call is used in a custom report. Note: All duration fields indicate time duration in milli seconds. b. The domain has data of all service calls made to this application and all custom metrics that were sent. Note: To view only Custom Metrics service-related data for an application, add a prefilter or filter while creating reports for Service ID equals "capturekonycustommetrics." 4. Expand Domains folder and select your domain. A domain represents a data set for which the user has defined custom metrics. The Domains folder shows domains for all applications in an account. a. There are two types of domains. Standard Metrics is the generic domain. It contains metrics collected for all applications deployed to development clouds in the cloud account. The Standard Metrics domain is available even if no custom metrics have been defined. This enables a user to build custom reports with the generic metrics that are captured for all their development clouds. The parameters captured are: i. Application Name ii. Application Type iii. Channel iv. Device Model 2015 by Kony, Inc. All rights reserved 50 of 124

51 v. Form ID vi. OS Version vii. Platform viii. Service ID ix. Timestamp_UTC -Timestamp of request in UTC x. Timestamp_Local -Timestamp when the service request was received in the timestamp set in a user's profile in manage cloud portal xi. ity, Country, Region, ZIP Code - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. xii. Internal Duration - Time spent by the service call in Kony App Services for internal processing xiii. External Duration - Time spent by the service call in Kony App Services for external call from Kony Server to backend xiv. PostProcessor Duration - Time spent by the service call in Kony app services in custom post-processing logic in the service xv. PreProcessor Duration - Time spent by the service call in Kony app services in custom pre-processing logic in the service xvi. Parse Duration - Time spent by the service call in Kony app services in parsing response from external source xvii. Total Duration - Total time spent in Kony app services server for the service call, from the time request was received by the server until the response was sent back to device. Total duration is equal to the sum of all the duration fields. The parameters Standard Metrics and Events are: Fields 2015 by Kony, Inc. All rights reserved 51 of 124

52 1. Application Name - Name of the application 2. App Type - Type of the application. For example, Native, SPA 3. Channel - Channel of application. For example, Mobile, Tablet 4. Platform - Application platform. For example, ios, Android 5. Device Model - Model of client device. 6. Kony User ID - User ID of the end user using app. Value has to be set using the setuserid API in the application. 7. DeviceID - Unique ID of the device for the application. 8. User Agent - User agent of the client device from network call 9. OS Version - Version of the client device's OS. 10. Service Group - Integration service name of the service request for applications defined from MobileFabric console. 11. Service ID - This param denotes operation name of the integration/orchestration service request for MobileFabric console defined apps. ServiceID of the service for apps where servicedefinition is defined from Kony Visualizer Enterprise. 12. City - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 13. Country - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 14. Region - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 15. Zip Code - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 16. Event Application Name - Name of the application from Events data by Kony, Inc. All rights reserved 52 of 124

53 17. Event App Type - Type of the application. For example, Native, SPA 18. Event Channel - Channel of application. For example, Mobile, Tablet 19. Event Platform - Application platform. For example, ios, Android 20. Event Device Model - Model of client device. 21. Event Kony User ID - User ID of the end user using app. Value has to be set using the setuserid API in the application. 22. Event DeviceID - Unique ID of the device for the application. 23. Event User Agent - User agent of the client device from network call 24. Event Application Version - Version of the client application 25. Plugin Version IDE - Plugin versions of Kony Visualizer Enterprise used for building the app. This will be populated only for Crash event type. 26. Plugin Version Platform - Plugin version of platform (like ios plugin) used for building the app. This will be populated only for Crash event type. 27. SDK Type - If app is built using Kony mobile fabric SDK this will indicate type of SDK like ios, PhoneGap. 28. SDK Version - Version of the mobile fabric SDK used in the client binary. 29. Event Type - Type of the application event. ex: FormEntry, Gesture 30. Event Sub Type - Event sub type of the application event. Meaning of subtype depends on the event type. For FormEntry event subtype denotes form entered. For Gesture it denotes type of Gesture like doubleclick. 31. Event Form ID - Form ID of the form where the application event occurred. 32. Event Widget ID - Widget Id of the widget where the application event was triggered. Not applicable for events that do not involve a widget like FormEntry, FormExit by Kony, Inc. All rights reserved 53 of 124

54 33. Event Flow Tag - Optional parameter that can be set by developer via an API call to identify a flow. Helps in easy identification for data analysis. 34. Error Code - Error code if the event type is error and Exception code if event type is exception. 35. Error message Error message. 36. Error Crash Report Crash Report from the device for event type Crash. Data is not symbolicated. 37. Custom Error Message Contains any custom message that is added by platform code or app developer to provide more info on error events. 38. Error File Application code file where error occurred. Applicable for event types Error/Exception if the same is available for type of error/exception. 39. Error Method Application function call where error occurred. Applicable for event types Error/Exception if the same is available for type of error/exception. 40. Error Stack Trace Stack trace of error. Applicable for event types Error/Crash if the same is available for type of error/crash. 41. Error Type Type of error. Ex: Error, Exception, Crash 42. Is Error true if the event type is error/crash and false if event type is exception. Not applicable for other event types. 43. Response Status Code Output status of the service response from the MobileFabric server 44. Events Meta Data Any meta data sent as part of the events data. Typically this is applicable for event type error, exception, crash, and custom. 45. Event TimeStamp_UTC Time stamp of event in UTC 46. Event TimeStamp_Local Time stamp of event in local time zone. Local time zone is set in user s profile in MobileFabric console by Kony, Inc. All rights reserved 54 of 124

55 47. Session TimeStamp_UTC Time stamp of session init in UTC 48. Session TimeStamp_Local Time stamp of session init in local time zone. Local time zone is set in user s profile in MobileFabric console. 49. Request TimeStamp_UTC Time stamp of service request in UTC 50. Request TimeStamp_Local Time stamp of service request in local time zone. Local time zone is set in user s profile in MobileFabric console. 51. Request MobileFabric app guid application guid generated on creation of an app in MobileFabric console. 52. Request MobileFabric app name application name provided on creation of an app in MobileFabric console. 53. Session MobileFabric app guid application guid generated on creation of an app in MobileFabric console. 54. Session MobileFabric app guid application name provided on creation of an app in MobileFabric console. 55. Object method Type of the object method ex. PUT, POST. Applicable for services with object mapping. 56. Object name Name of the object that is mapped in service request. Applicable for services with object mapping. 57. Integration service version header Version of the integration service requested by application in the service request header. 58. Integration service version Version of the integration service served by the application server for a service request. Measures: 1. Internal Duration - Time spent by the service call in Kony App Services for internal processing 2015 by Kony, Inc. All rights reserved 55 of 124

56 2. External Duration - Time spent by the service call in Kony App Services for external call from Kony Server to backend 3. PostProcessor Duration - Time spent by the service call in Kony app services in custom post-processing logic in the service 4. PreProcessor Duration - Time spent by the service call in Kony app services in custom pre-processing logic in the service 5. Parse Duration - Time spent by the service call in Kony app services in parsing response from external source 6. Total Duration - Total time spent in Kony app services server for the service call, from the time request was received by the server until the response was sent back to device. Total duration is equal to the sum of all the duration fields. 7. Error Line Line number in application code file where error occurred. Applicable for event types error/exception. 8. HTTP Response Code HTTP code of the service response obtained by the device. 9. Response Time Response time as viewed by the client device. That is time since service request is sent from device to server and response obtained back in the device. 10. Event Session Key Unique session identifier for the session in which the application event occurred. 11. Middleware Session Key Unique session identifier for application session data from session init call. 12. Object mapping duration (request) Time taken to map the object detail into service request by Kony app services. 13. Object mapping duration (response) Time taken to map the object detail into service response by Kony app services by Kony, Inc. All rights reserved 56 of 124

57 14. Count Sample custom field created to show count of application. This is to function as a count(*) for application session and service request calls. Note: Similar data is sometimes made available for different types of data like Events, Session, Service Requests, Error as data is stored in different tables for them and having different fields called out enables a more optimized query to run if only one type of network call is used in a custom report. Note: All duration fields indicate time duration in milli seconds. b. The domain has data of all service calls made to this application and all custom metrics that were sent. Note: To view only Custom Metrics service-related data for an application, add a prefilter or filter while creating reports for Service ID equals "capturekonycustommetrics." 5. Expand Domains folder and select your domain. A domain represents a data set for which the user has defined custom metrics. The Domains folder shows domains for all applications in an account. a. There are two types of domains. Standard Metrics is the generic domain. It contains metrics collected for all applications deployed to development clouds in the cloud account. The Standard Metrics domain is available even if no custom metrics have been defined. This enables a user to build custom reports with the generic metrics that are captured for all their development clouds. The parameters captured are: i. Application Name ii. Application Type iii. Channel iv. Device Model 2015 by Kony, Inc. All rights reserved 57 of 124

58 v. Form ID vi. OS Version vii. Platform viii. Service ID ix. Timestamp_UTC -Timestamp of request in UTC x. Timestamp_Local -Timestamp when the service request was received in the timestamp set in a user's profile in manage cloud portal xi. ity, Country, Region, ZIP Code - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. xii. Internal Duration - Time spent by the service call in Kony App Services for internal processing xiii. External Duration - Time spent by the service call in Kony App Services for external call from Kony Server to backend xiv. PostProcessor Duration - Time spent by the service call in Kony app services in custom post-processing logic in the service xv. PreProcessor Duration - Time spent by the service call in Kony app services in custom pre-processing logic in the service xvi. Parse Duration - Time spent by the service call in Kony app services in parsing response from external source xvii. Total Duration - Total time spent in Kony app services server for the service call, from the time request was received by the server until the response was sent back to device. Total duration is equal to the sum of all the duration fields. The parameters Standard Metrics and Events are: Fields 2015 by Kony, Inc. All rights reserved 58 of 124

59 1. Application Name - Name of the application 2. App Type - Type of the application. For example, Native, SPA 3. Channel - Channel of application. For example, Mobile, Tablet 4. Platform - Application platform. For example, ios, Android 5. Device Model - Model of client device. 6. Kony User ID - User ID of the end user using app. Value has to be set using the setuserid API in the application. 7. DeviceID - Unique ID of the device for the application. 8. User Agent - User agent of the client device from network call 9. OS Version - Version of the client device's OS. 10. Service Group - Integration service name of the service request for applications defined from MobileFabric console. 11. Service ID - This param denotes operation name of the integration/orchestration service request for MobileFabric console defined apps. ServiceID of the service for apps where servicedefinition is defined from Kony Visualizer Enterprise. 12. City - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 13. Country - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 14. Region - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 15. Zip Code - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 16. Event Application Name - Name of the application from Events data by Kony, Inc. All rights reserved 59 of 124

60 17. Event App Type - Type of the application. For example, Native, SPA 18. Event Channel - Channel of application. For example, Mobile, Tablet 19. Event Platform - Application platform. For example, ios, Android 20. Event Device Model - Model of client device. 21. Event Kony User ID - User ID of the end user using app. Value has to be set using the setuserid API in the application. 22. Event DeviceID - Unique ID of the device for the application. 23. Event User Agent - User agent of the client device from network call 24. Event Application Version - Version of the client application 25. Plugin Version IDE - Plugin versions of Kony Visualizer Enterprise used for building the app. This will be populated only for Crash event type. 26. Plugin Version Platform - Plugin version of platform (like ios plugin) used for building the app. This will be populated only for Crash event type. 27. SDK Type - If app is built using Kony mobile fabric SDK this will indicate type of SDK like ios, PhoneGap. 28. SDK Version - Version of the mobile fabric SDK used in the client binary. 29. Event Type - Type of the application event. ex: FormEntry, Gesture 30. Event Sub Type - Event sub type of the application event. Meaning of subtype depends on the event type. For FormEntry event subtype denotes form entered. For Gesture it denotes type of Gesture like doubleclick. 31. Event Form ID - Form ID of the form where the application event occurred. 32. Event Widget ID - Widget Id of the widget where the application event was triggered. Not applicable for events that do not involve a widget like FormEntry, FormExit by Kony, Inc. All rights reserved 60 of 124

61 33. Event Flow Tag - Optional parameter that can be set by developer via an API call to identify a flow. Helps in easy identification for data analysis. 34. Error Code - Error code if the event type is error and Exception code if event type is exception. 35. Error message Error message. 36. Error Crash Report Crash Report from the device for event type Crash. Data is not symbolicated. 37. Custom Error Message Contains any custom message that is added by platform code or app developer to provide more info on error events. 38. Error File Application code file where error occurred. Applicable for event types Error/Exception if the same is available for type of error/exception. 39. Error Method Application function call where error occurred. Applicable for event types Error/Exception if the same is available for type of error/exception. 40. Error Stack Trace Stack trace of error. Applicable for event types Error/Crash if the same is available for type of error/crash. 41. Error Type Type of error. Ex: Error, Exception, Crash 42. Is Error true if the event type is error/crash and false if event type is exception. Not applicable for other event types. 43. Response Status Code Output status of the service response from the MobileFabric server 44. Events Meta Data Any meta data sent as part of the events data. Typically this is applicable for event type error, exception, crash, and custom. 45. Event TimeStamp_UTC Time stamp of event in UTC 46. Event TimeStamp_Local Time stamp of event in local time zone. Local time zone is set in user s profile in MobileFabric console by Kony, Inc. All rights reserved 61 of 124

62 47. Session TimeStamp_UTC Time stamp of session init in UTC 48. Session TimeStamp_Local Time stamp of session init in local time zone. Local time zone is set in user s profile in MobileFabric console. 49. Request TimeStamp_UTC Time stamp of service request in UTC 50. Request TimeStamp_Local Time stamp of service request in local time zone. Local time zone is set in user s profile in MobileFabric console. 51. Request MobileFabric app guid application guid generated on creation of an app in MobileFabric console. 52. Request MobileFabric app name application name provided on creation of an app in MobileFabric console. 53. Session MobileFabric app guid application guid generated on creation of an app in MobileFabric console. 54. Session MobileFabric app guid application name provided on creation of an app in MobileFabric console. 55. Object method Type of the object method ex. PUT, POST. Applicable for services with object mapping. 56. Object name Name of the object that is mapped in service request. Applicable for services with object mapping. 57. Integration service version header Version of the integration service requested by application in the service request header. 58. Integration service version Version of the integration service served by the application server for a service request. Measures: 1. Internal Duration - Time spent by the service call in Kony App Services for internal processing 2015 by Kony, Inc. All rights reserved 62 of 124

63 2. External Duration - Time spent by the service call in Kony App Services for external call from Kony Server to backend 3. PostProcessor Duration - Time spent by the service call in Kony app services in custom post-processing logic in the service 4. PreProcessor Duration - Time spent by the service call in Kony app services in custom pre-processing logic in the service 5. Parse Duration - Time spent by the service call in Kony app services in parsing response from external source 6. Total Duration - Total time spent in Kony app services server for the service call, from the time request was received by the server until the response was sent back to device. Total duration is equal to the sum of all the duration fields. 7. Error Line Line number in application code file where error occurred. Applicable for event types error/exception. 8. HTTP Response Code HTTP code of the service response obtained by the device. 9. Response Time Response time as viewed by the client device. That is time since service request is sent from device to server and response obtained back in the device. 10. Event Session Key Unique session identifier for the session in which the application event occurred. 11. Middleware Session Key Unique session identifier for application session data from session init call. 12. Object mapping duration (request) Time taken to map the object detail into service request by Kony app services. 13. Object mapping duration (response) Time taken to map the object detail into service response by Kony app services by Kony, Inc. All rights reserved 63 of 124

64 14. Count Sample custom field created to show count of application. This is to function as a count(*) for application session and service request calls. Note: Similar data is sometimes made available for different types of data like Events, Session, Service Requests, Error as data is stored in different tables for them and having different fields called out enables a more optimized query to run if only one type of network call is used in a custom report. Note: All duration fields indicate time duration in milli seconds. b. The domain has data of all service calls made to this application and all custom metrics that were sent. Note: To view only Custom Metrics service-related data for an application, add a prefilter or filter while creating reports for Service ID equals "capturekonycustommetrics." 6. Expand Domains folder and select your domain. A domain represents a data set for which the user has defined custom metrics. The Domains folder shows domains for all applications in an account. a. There are two types of domains. Standard Metrics is the generic domain. It contains metrics collected for all applications deployed to development clouds in the cloud account. The Standard Metrics domain is available even if no custom metrics have been defined. This enables a user to build custom reports with the generic metrics that are captured for all their development clouds. The parameters captured are: i. Application Name ii. Application Type iii. Channel iv. Device Model 2015 by Kony, Inc. All rights reserved 64 of 124

65 v. Form ID vi. OS Version vii. Platform viii. Service ID ix. Timestamp_UTC -Timestamp of request in UTC x. Timestamp_Local -Timestamp when the service request was received in the timestamp set in a user's profile in manage cloud portal xi. ity, Country, Region, ZIP Code - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. xii. Internal Duration - Time spent by the service call in Kony App Services for internal processing xiii. External Duration - Time spent by the service call in Kony App Services for external call from Kony Server to backend xiv. PostProcessor Duration - Time spent by the service call in Kony app services in custom post-processing logic in the service xv. PreProcessor Duration - Time spent by the service call in Kony app services in custom pre-processing logic in the service xvi. Parse Duration - Time spent by the service call in Kony app services in parsing response from external source xvii. Total Duration - Total time spent in Kony app services server for the service call, from the time request was received by the server until the response was sent back to device. Total duration is equal to the sum of all the duration fields. The parameters Standard Metrics and Events are: Fields 2015 by Kony, Inc. All rights reserved 65 of 124

66 1. Application Name - Name of the application 2. App Type - Type of the application. For example, Native, SPA 3. Channel - Channel of application. For example, Mobile, Tablet 4. Platform - Application platform. For example, ios, Android 5. Device Model - Model of client device. 6. Kony User ID - User ID of the end user using app. Value has to be set using the setuserid API in the application. 7. DeviceID - Unique ID of the device for the application. 8. User Agent - User agent of the client device from network call 9. OS Version - Version of the client device's OS. 10. Service Group - Integration service name of the service request for applications defined from MobileFabric console. 11. Service ID - This param denotes operation name of the integration/orchestration service request for MobileFabric console defined apps. ServiceID of the service for apps where servicedefinition is defined from Kony Visualizer Enterprise. 12. City - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 13. Country - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 14. Region - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 15. Zip Code - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 16. Event Application Name - Name of the application from Events data by Kony, Inc. All rights reserved 66 of 124

67 17. Event App Type - Type of the application. For example, Native, SPA 18. Event Channel - Channel of application. For example, Mobile, Tablet 19. Event Platform - Application platform. For example, ios, Android 20. Event Device Model - Model of client device. 21. Event Kony User ID - User ID of the end user using app. Value has to be set using the setuserid API in the application. 22. Event DeviceID - Unique ID of the device for the application. 23. Event User Agent - User agent of the client device from network call 24. Event Application Version - Version of the client application 25. Plugin Version IDE - Plugin versions of Kony Visualizer Enterprise used for building the app. This will be populated only for Crash event type. 26. Plugin Version Platform - Plugin version of platform (like ios plugin) used for building the app. This will be populated only for Crash event type. 27. SDK Type - If app is built using Kony mobile fabric SDK this will indicate type of SDK like ios, PhoneGap. 28. SDK Version - Version of the mobile fabric SDK used in the client binary. 29. Event Type - Type of the application event. ex: FormEntry, Gesture 30. Event Sub Type - Event sub type of the application event. Meaning of subtype depends on the event type. For FormEntry event subtype denotes form entered. For Gesture it denotes type of Gesture like doubleclick. 31. Event Form ID - Form ID of the form where the application event occurred. 32. Event Widget ID - Widget Id of the widget where the application event was triggered. Not applicable for events that do not involve a widget like FormEntry, FormExit by Kony, Inc. All rights reserved 67 of 124

68 33. Event Flow Tag - Optional parameter that can be set by developer via an API call to identify a flow. Helps in easy identification for data analysis. 34. Error Code - Error code if the event type is error and Exception code if event type is exception. 35. Error message Error message. 36. Error Crash Report Crash Report from the device for event type Crash. Data is not symbolicated. 37. Custom Error Message Contains any custom message that is added by platform code or app developer to provide more info on error events. 38. Error File Application code file where error occurred. Applicable for event types Error/Exception if the same is available for type of error/exception. 39. Error Method Application function call where error occurred. Applicable for event types Error/Exception if the same is available for type of error/exception. 40. Error Stack Trace Stack trace of error. Applicable for event types Error/Crash if the same is available for type of error/crash. 41. Error Type Type of error. Ex: Error, Exception, Crash 42. Is Error true if the event type is error/crash and false if event type is exception. Not applicable for other event types. 43. Response Status Code Output status of the service response from the MobileFabric server 44. Events Meta Data Any meta data sent as part of the events data. Typically this is applicable for event type error, exception, crash, and custom. 45. Event TimeStamp_UTC Time stamp of event in UTC 46. Event TimeStamp_Local Time stamp of event in local time zone. Local time zone is set in user s profile in MobileFabric console by Kony, Inc. All rights reserved 68 of 124

69 47. Session TimeStamp_UTC Time stamp of session init in UTC 48. Session TimeStamp_Local Time stamp of session init in local time zone. Local time zone is set in user s profile in MobileFabric console. 49. Request TimeStamp_UTC Time stamp of service request in UTC 50. Request TimeStamp_Local Time stamp of service request in local time zone. Local time zone is set in user s profile in MobileFabric console. 51. Request MobileFabric app guid application guid generated on creation of an app in MobileFabric console. 52. Request MobileFabric app name application name provided on creation of an app in MobileFabric console. 53. Session MobileFabric app guid application guid generated on creation of an app in MobileFabric console. 54. Session MobileFabric app guid application name provided on creation of an app in MobileFabric console. 55. Object method Type of the object method ex. PUT, POST. Applicable for services with object mapping. 56. Object name Name of the object that is mapped in service request. Applicable for services with object mapping. 57. Integration service version header Version of the integration service requested by application in the service request header. 58. Integration service version Version of the integration service served by the application server for a service request. Measures: 1. Internal Duration - Time spent by the service call in Kony App Services for internal processing 2015 by Kony, Inc. All rights reserved 69 of 124

70 2. External Duration - Time spent by the service call in Kony App Services for external call from Kony Server to backend 3. PostProcessor Duration - Time spent by the service call in Kony app services in custom post-processing logic in the service 4. PreProcessor Duration - Time spent by the service call in Kony app services in custom pre-processing logic in the service 5. Parse Duration - Time spent by the service call in Kony app services in parsing response from external source 6. Total Duration - Total time spent in Kony app services server for the service call, from the time request was received by the server until the response was sent back to device. Total duration is equal to the sum of all the duration fields. 7. Error Line Line number in application code file where error occurred. Applicable for event types error/exception. 8. HTTP Response Code HTTP code of the service response obtained by the device. 9. Response Time Response time as viewed by the client device. That is time since service request is sent from device to server and response obtained back in the device. 10. Event Session Key Unique session identifier for the session in which the application event occurred. 11. Middleware Session Key Unique session identifier for application session data from session init call. 12. Object mapping duration (request) Time taken to map the object detail into service request by Kony app services. 13. Object mapping duration (response) Time taken to map the object detail into service response by Kony app services by Kony, Inc. All rights reserved 70 of 124

71 14. Count Sample custom field created to show count of application. This is to function as a count(*) for application session and service request calls. Note: Similar data is sometimes made available for different types of data like Events, Session, Service Requests, Error as data is stored in different tables for them and having different fields called out enables a more optimized query to run if only one type of network call is used in a custom report. Note: All duration fields indicate time duration in milli seconds. b. The domain has data of all service calls made to this application and all custom metrics that were sent. Note: To view only Custom Metrics service-related data for an application, add a prefilter or filter while creating reports for Service ID equals "capturekonycustommetrics." 7. Expand Domains folder and select your domain. A domain represents a data set for which the user has defined custom metrics. The Domains folder shows domains for all applications in an account. a. There are two types of domains. Standard Metrics is the generic domain. It contains metrics collected for all applications deployed to development clouds in the cloud account. The Standard Metrics domain is available even if no custom metrics have been defined. This enables a user to build custom reports with the generic metrics that are captured for all their development clouds. The parameters captured are: i. Application Name ii. Application Type iii. Channel iv. Device Model 2015 by Kony, Inc. All rights reserved 71 of 124

72 v. Form ID vi. OS Version vii. Platform viii. Service ID ix. Timestamp_UTC -Timestamp of request in UTC x. Timestamp_Local -Timestamp when the service request was received in the timestamp set in a user's profile in manage cloud portal xi. ity, Country, Region, ZIP Code - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. xii. Internal Duration - Time spent by the service call in Kony App Services for internal processing xiii. External Duration - Time spent by the service call in Kony App Services for external call from Kony Server to backend xiv. PostProcessor Duration - Time spent by the service call in Kony app services in custom post-processing logic in the service xv. PreProcessor Duration - Time spent by the service call in Kony app services in custom pre-processing logic in the service xvi. Parse Duration - Time spent by the service call in Kony app services in parsing response from external source xvii. Total Duration - Total time spent in Kony app services server for the service call, from the time request was received by the server until the response was sent back to device. Total duration is equal to the sum of all the duration fields. The parameters Standard Metrics and Events are: Fields 2015 by Kony, Inc. All rights reserved 72 of 124

73 1. Application Name - Name of the application 2. App Type - Type of the application. For example, Native, SPA 3. Channel - Channel of application. For example, Mobile, Tablet 4. Platform - Application platform. For example, ios, Android 5. Device Model - Model of client device. 6. Kony User ID - User ID of the end user using app. Value has to be set using the setuserid API in the application. 7. DeviceID - Unique ID of the device for the application. 8. User Agent - User agent of the client device from network call 9. OS Version - Version of the client device's OS. 10. Service Group - Integration service name of the service request for applications defined from MobileFabric console. 11. Service ID - This param denotes operation name of the integration/orchestration service request for MobileFabric console defined apps. ServiceID of the service for apps where servicedefinition is defined from Kony Visualizer Enterprise. 12. City - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 13. Country - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 14. Region - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 15. Zip Code - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 16. Event Application Name - Name of the application from Events data by Kony, Inc. All rights reserved 73 of 124

74 17. Event App Type - Type of the application. For example, Native, SPA 18. Event Channel - Channel of application. For example, Mobile, Tablet 19. Event Platform - Application platform. For example, ios, Android 20. Event Device Model - Model of client device. 21. Event Kony User ID - User ID of the end user using app. Value has to be set using the setuserid API in the application. 22. Event DeviceID - Unique ID of the device for the application. 23. Event User Agent - User agent of the client device from network call 24. Event Application Version - Version of the client application 25. Plugin Version IDE - Plugin versions of Kony Visualizer Enterprise used for building the app. This will be populated only for Crash event type. 26. Plugin Version Platform - Plugin version of platform (like ios plugin) used for building the app. This will be populated only for Crash event type. 27. SDK Type - If app is built using Kony mobile fabric SDK this will indicate type of SDK like ios, PhoneGap. 28. SDK Version - Version of the mobile fabric SDK used in the client binary. 29. Event Type - Type of the application event. ex: FormEntry, Gesture 30. Event Sub Type - Event sub type of the application event. Meaning of subtype depends on the event type. For FormEntry event subtype denotes form entered. For Gesture it denotes type of Gesture like doubleclick. 31. Event Form ID - Form ID of the form where the application event occurred. 32. Event Widget ID - Widget Id of the widget where the application event was triggered. Not applicable for events that do not involve a widget like FormEntry, FormExit by Kony, Inc. All rights reserved 74 of 124

75 33. Event Flow Tag - Optional parameter that can be set by developer via an API call to identify a flow. Helps in easy identification for data analysis. 34. Error Code - Error code if the event type is error and Exception code if event type is exception. 35. Error message Error message. 36. Error Crash Report Crash Report from the device for event type Crash. Data is not symbolicated. 37. Custom Error Message Contains any custom message that is added by platform code or app developer to provide more info on error events. 38. Error File Application code file where error occurred. Applicable for event types Error/Exception if the same is available for type of error/exception. 39. Error Method Application function call where error occurred. Applicable for event types Error/Exception if the same is available for type of error/exception. 40. Error Stack Trace Stack trace of error. Applicable for event types Error/Crash if the same is available for type of error/crash. 41. Error Type Type of error. Ex: Error, Exception, Crash 42. Is Error true if the event type is error/crash and false if event type is exception. Not applicable for other event types. 43. Response Status Code Output status of the service response from the MobileFabric server 44. Events Meta Data Any meta data sent as part of the events data. Typically this is applicable for event type error, exception, crash, and custom. 45. Event TimeStamp_UTC Time stamp of event in UTC 46. Event TimeStamp_Local Time stamp of event in local time zone. Local time zone is set in user s profile in MobileFabric console by Kony, Inc. All rights reserved 75 of 124

76 47. Session TimeStamp_UTC Time stamp of session init in UTC 48. Session TimeStamp_Local Time stamp of session init in local time zone. Local time zone is set in user s profile in MobileFabric console. 49. Request TimeStamp_UTC Time stamp of service request in UTC 50. Request TimeStamp_Local Time stamp of service request in local time zone. Local time zone is set in user s profile in MobileFabric console. 51. Request MobileFabric app guid application guid generated on creation of an app in MobileFabric console. 52. Request MobileFabric app name application name provided on creation of an app in MobileFabric console. 53. Session MobileFabric app guid application guid generated on creation of an app in MobileFabric console. 54. Session MobileFabric app guid application name provided on creation of an app in MobileFabric console. 55. Object method Type of the object method ex. PUT, POST. Applicable for services with object mapping. 56. Object name Name of the object that is mapped in service request. Applicable for services with object mapping. 57. Integration service version header Version of the integration service requested by application in the service request header. 58. Integration service version Version of the integration service served by the application server for a service request. Measures: 1. Internal Duration - Time spent by the service call in Kony App Services for internal processing 2015 by Kony, Inc. All rights reserved 76 of 124

77 2. External Duration - Time spent by the service call in Kony App Services for external call from Kony Server to backend 3. PostProcessor Duration - Time spent by the service call in Kony app services in custom post-processing logic in the service 4. PreProcessor Duration - Time spent by the service call in Kony app services in custom pre-processing logic in the service 5. Parse Duration - Time spent by the service call in Kony app services in parsing response from external source 6. Total Duration - Total time spent in Kony app services server for the service call, from the time request was received by the server until the response was sent back to device. Total duration is equal to the sum of all the duration fields. 7. Error Line Line number in application code file where error occurred. Applicable for event types error/exception. 8. HTTP Response Code HTTP code of the service response obtained by the device. 9. Response Time Response time as viewed by the client device. That is time since service request is sent from device to server and response obtained back in the device. 10. Event Session Key Unique session identifier for the session in which the application event occurred. 11. Middleware Session Key Unique session identifier for application session data from session init call. 12. Object mapping duration (request) Time taken to map the object detail into service request by Kony app services. 13. Object mapping duration (response) Time taken to map the object detail into service response by Kony app services by Kony, Inc. All rights reserved 77 of 124

78 14. Count Sample custom field created to show count of application. This is to function as a count(*) for application session and service request calls. Note: Similar data is sometimes made available for different types of data like Events, Session, Service Requests, Error as data is stored in different tables for them and having different fields called out enables a more optimized query to run if only one type of network call is used in a custom report. Note: All duration fields indicate time duration in milli seconds. b. The domain has data of all service calls made to this application and all custom metrics that were sent. Note: To view only Custom Metrics service-related data for an application, add a prefilter or filter while creating reports for Service ID equals "capturekonycustommetrics." 8. Expand Domains folder and select your domain. A domain represents a data set for which the user has defined custom metrics. The Domains folder shows domains for all applications in an account. a. There are two types of domains. Standard Metrics is the generic domain. It contains metrics collected for all applications deployed to development clouds in the cloud account. The Standard Metrics domain is available even if no custom metrics have been defined. This enables a user to build custom reports with the generic metrics that are captured for all their development clouds. The parameters captured are: i. Application Name ii. Application Type iii. Channel iv. Device Model 2015 by Kony, Inc. All rights reserved 78 of 124

79 v. Form ID vi. OS Version vii. Platform viii. Service ID ix. Timestamp_UTC -Timestamp of request in UTC x. Timestamp_Local -Timestamp when the service request was received in the timestamp set in a user's profile in manage cloud portal xi. ity, Country, Region, ZIP Code - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. xii. Internal Duration - Time spent by the service call in Kony App Services for internal processing xiii. External Duration - Time spent by the service call in Kony App Services for external call from Kony Server to backend xiv. PostProcessor Duration - Time spent by the service call in Kony app services in custom post-processing logic in the service xv. PreProcessor Duration - Time spent by the service call in Kony app services in custom pre-processing logic in the service xvi. Parse Duration - Time spent by the service call in Kony app services in parsing response from external source xvii. Total Duration - Total time spent in Kony app services server for the service call, from the time request was received by the server until the response was sent back to device. Total duration is equal to the sum of all the duration fields. The parameters Standard Metrics and Events are: Fields 2015 by Kony, Inc. All rights reserved 79 of 124

80 1. Application Name - Name of the application 2. App Type - Type of the application. For example, Native, SPA 3. Channel - Channel of application. For example, Mobile, Tablet 4. Platform - Application platform. For example, ios, Android 5. Device Model - Model of client device. 6. Kony User ID - User ID of the end user using app. Value has to be set using the setuserid API in the application. 7. DeviceID - Unique ID of the device for the application. 8. User Agent - User agent of the client device from network call 9. OS Version - Version of the client device's OS. 10. Service Group - Integration service name of the service request for applications defined from MobileFabric console. 11. Service ID - This param denotes operation name of the integration/orchestration service request for MobileFabric console defined apps. ServiceID of the service for apps where servicedefinition is defined from Kony Visualizer Enterprise. 12. City - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 13. Country - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 14. Region - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 15. Zip Code - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 16. Event Application Name - Name of the application from Events data by Kony, Inc. All rights reserved 80 of 124

81 17. Event App Type - Type of the application. For example, Native, SPA 18. Event Channel - Channel of application. For example, Mobile, Tablet 19. Event Platform - Application platform. For example, ios, Android 20. Event Device Model - Model of client device. 21. Event Kony User ID - User ID of the end user using app. Value has to be set using the setuserid API in the application. 22. Event DeviceID - Unique ID of the device for the application. 23. Event User Agent - User agent of the client device from network call 24. Event Application Version - Version of the client application 25. Plugin Version IDE - Plugin versions of Kony Visualizer Enterprise used for building the app. This will be populated only for Crash event type. 26. Plugin Version Platform - Plugin version of platform (like ios plugin) used for building the app. This will be populated only for Crash event type. 27. SDK Type - If app is built using Kony mobile fabric SDK this will indicate type of SDK like ios, PhoneGap. 28. SDK Version - Version of the mobile fabric SDK used in the client binary. 29. Event Type - Type of the application event. ex: FormEntry, Gesture 30. Event Sub Type - Event sub type of the application event. Meaning of subtype depends on the event type. For FormEntry event subtype denotes form entered. For Gesture it denotes type of Gesture like doubleclick. 31. Event Form ID - Form ID of the form where the application event occurred. 32. Event Widget ID - Widget Id of the widget where the application event was triggered. Not applicable for events that do not involve a widget like FormEntry, FormExit by Kony, Inc. All rights reserved 81 of 124

82 33. Event Flow Tag - Optional parameter that can be set by developer via an API call to identify a flow. Helps in easy identification for data analysis. 34. Error Code - Error code if the event type is error and Exception code if event type is exception. 35. Error message Error message. 36. Error Crash Report Crash Report from the device for event type Crash. Data is not symbolicated. 37. Custom Error Message Contains any custom message that is added by platform code or app developer to provide more info on error events. 38. Error File Application code file where error occurred. Applicable for event types Error/Exception if the same is available for type of error/exception. 39. Error Method Application function call where error occurred. Applicable for event types Error/Exception if the same is available for type of error/exception. 40. Error Stack Trace Stack trace of error. Applicable for event types Error/Crash if the same is available for type of error/crash. 41. Error Type Type of error. Ex: Error, Exception, Crash 42. Is Error true if the event type is error/crash and false if event type is exception. Not applicable for other event types. 43. Response Status Code Output status of the service response from the MobileFabric server 44. Events Meta Data Any meta data sent as part of the events data. Typically this is applicable for event type error, exception, crash, and custom. 45. Event TimeStamp_UTC Time stamp of event in UTC 46. Event TimeStamp_Local Time stamp of event in local time zone. Local time zone is set in user s profile in MobileFabric console by Kony, Inc. All rights reserved 82 of 124

83 47. Session TimeStamp_UTC Time stamp of session init in UTC 48. Session TimeStamp_Local Time stamp of session init in local time zone. Local time zone is set in user s profile in MobileFabric console. 49. Request TimeStamp_UTC Time stamp of service request in UTC 50. Request TimeStamp_Local Time stamp of service request in local time zone. Local time zone is set in user s profile in MobileFabric console. 51. Request MobileFabric app guid application guid generated on creation of an app in MobileFabric console. 52. Request MobileFabric app name application name provided on creation of an app in MobileFabric console. 53. Session MobileFabric app guid application guid generated on creation of an app in MobileFabric console. 54. Session MobileFabric app guid application name provided on creation of an app in MobileFabric console. 55. Object method Type of the object method ex. PUT, POST. Applicable for services with object mapping. 56. Object name Name of the object that is mapped in service request. Applicable for services with object mapping. 57. Integration service version header Version of the integration service requested by application in the service request header. 58. Integration service version Version of the integration service served by the application server for a service request. Measures: 1. Internal Duration - Time spent by the service call in Kony App Services for internal processing 2015 by Kony, Inc. All rights reserved 83 of 124

84 2. External Duration - Time spent by the service call in Kony App Services for external call from Kony Server to backend 3. PostProcessor Duration - Time spent by the service call in Kony app services in custom post-processing logic in the service 4. PreProcessor Duration - Time spent by the service call in Kony app services in custom pre-processing logic in the service 5. Parse Duration - Time spent by the service call in Kony app services in parsing response from external source 6. Total Duration - Total time spent in Kony app services server for the service call, from the time request was received by the server until the response was sent back to device. Total duration is equal to the sum of all the duration fields. 7. Error Line Line number in application code file where error occurred. Applicable for event types error/exception. 8. HTTP Response Code HTTP code of the service response obtained by the device. 9. Response Time Response time as viewed by the client device. That is time since service request is sent from device to server and response obtained back in the device. 10. Event Session Key Unique session identifier for the session in which the application event occurred. 11. Middleware Session Key Unique session identifier for application session data from session init call. 12. Object mapping duration (request) Time taken to map the object detail into service request by Kony app services. 13. Object mapping duration (response) Time taken to map the object detail into service response by Kony app services by Kony, Inc. All rights reserved 84 of 124

85 14. Count Sample custom field created to show count of application. This is to function as a count(*) for application session and service request calls. Note: Similar data is sometimes made available for different types of data like Events, Session, Service Requests, Error as data is stored in different tables for them and having different fields called out enables a more optimized query to run if only one type of network call is used in a custom report. Note: All duration fields indicate time duration in milli seconds. b. The domain has data of all service calls made to this application and all custom metrics that were sent. Note: To view only Custom Metrics service-related data for an application, add a prefilter or filter while creating reports for Service ID equals "capturekonycustommetrics." 9. Expand Domains folder and select your domain. A domain represents a data set for which the user has defined custom metrics. The Domains folder shows domains for all applications in an account. a. There are two types of domains. Standard Metrics is the generic domain. It contains metrics collected for all applications deployed to development clouds in the cloud account. The Standard Metrics domain is available even if no custom metrics have been defined. This enables a user to build custom reports with the generic metrics that are captured for all their development clouds. The parameters captured are: i. Application Name ii. Application Type iii. Channel iv. Device Model 2015 by Kony, Inc. All rights reserved 85 of 124

86 v. Form ID vi. OS Version vii. Platform viii. Service ID ix. Timestamp_UTC -Timestamp of request in UTC x. Timestamp_Local -Timestamp when the service request was received in the timestamp set in a user's profile in manage cloud portal xi. ity, Country, Region, ZIP Code - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. xii. Internal Duration - Time spent by the service call in Kony App Services for internal processing xiii. External Duration - Time spent by the service call in Kony App Services for external call from Kony Server to backend xiv. PostProcessor Duration - Time spent by the service call in Kony app services in custom post-processing logic in the service xv. PreProcessor Duration - Time spent by the service call in Kony app services in custom pre-processing logic in the service xvi. Parse Duration - Time spent by the service call in Kony app services in parsing response from external source xvii. Total Duration - Total time spent in Kony app services server for the service call, from the time request was received by the server until the response was sent back to device. Total duration is equal to the sum of all the duration fields. The parameters Standard Metrics and Events are: Fields 2015 by Kony, Inc. All rights reserved 86 of 124

87 1. Application Name - Name of the application 2. App Type - Type of the application. For example, Native, SPA 3. Channel - Channel of application. For example, Mobile, Tablet 4. Platform - Application platform. For example, ios, Android 5. Device Model - Model of client device. 6. Kony User ID - User ID of the end user using app. Value has to be set using the setuserid API in the application. 7. DeviceID - Unique ID of the device for the application. 8. User Agent - User agent of the client device from network call 9. OS Version - Version of the client device's OS. 10. Service Group - Integration service name of the service request for applications defined from MobileFabric console. 11. Service ID - This param denotes operation name of the integration/orchestration service request for MobileFabric console defined apps. ServiceID of the service for apps where servicedefinition is defined from Kony Visualizer Enterprise. 12. City - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 13. Country - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 14. Region - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 15. Zip Code - Obtained from IP for geolocation mapping. This field is not populated if this detail cannot be resolved from the IP address. 16. Event Application Name - Name of the application from Events data by Kony, Inc. All rights reserved 87 of 124

88 17. Event App Type - Type of the application. For example, Native, SPA 18. Event Channel - Channel of application. For example, Mobile, Tablet 19. Event Platform - Application platform. For example, ios, Android 20. Event Device Model - Model of client device. 21. Event Kony User ID - User ID of the end user using app. Value has to be set using the setuserid API in the application. 22. Event DeviceID - Unique ID of the device for the application. 23. Event User Agent - User agent of the client device from network call 24. Event Application Version - Version of the client application 25. Plugin Version IDE - Plugin versions of Kony Visualizer Enterprise used for building the app. This will be populated only for Crash event type. 26. Plugin Version Platform - Plugin version of platform (like ios plugin) used for building the app. This will be populated only for Crash event type. 27. SDK Type - If app is built using Kony mobile fabric SDK this will indicate type of SDK like ios, PhoneGap. 28. SDK Version - Version of the mobile fabric SDK used in the client binary. 29. Event Type - Type of the application event. ex: FormEntry, Gesture 30. Event Sub Type - Event sub type of the application event. Meaning of subtype depends on the event type. For FormEntry event subtype denotes form entered. For Gesture it denotes type of Gesture like doubleclick. 31. Event Form ID - Form ID of the form where the application event occurred. 32. Event Widget ID - Widget Id of the widget where the application event was triggered. Not applicable for events that do not involve a widget like FormEntry, FormExit by Kony, Inc. All rights reserved 88 of 124

89 33. Event Flow Tag - Optional parameter that can be set by developer via an API call to identify a flow. Helps in easy identification for data analysis. 34. Error Code - Error code if the event type is error and Exception code if event type is exception. 35. Error message Error message. 36. Error Crash Report Crash Report from the device for event type Crash. Data is not symbolicated. 37. Custom Error Message Contains any custom message that is added by platform code or app developer to provide more info on error events. 38. Error File Application code file where error occurred. Applicable for event types Error/Exception if the same is available for type of error/exception. 39. Error Method Application function call where error occurred. Applicable for event types Error/Exception if the same is available for type of error/exception. 40. Error Stack Trace Stack trace of error. Applicable for event types Error/Crash if the same is available for type of error/crash. 41. Error Type Type of error. Ex: Error, Exception, Crash 42. Is Error true if the event type is error/crash and false if event type is exception. Not applicable for other event types. 43. Response Status Code Output status of the service response from the MobileFabric server 44. Events Meta Data Any meta data sent as part of the events data. Typically this is applicable for event type error, exception, crash, and custom. 45. Event TimeStamp_UTC Time stamp of event in UTC 46. Event TimeStamp_Local Time stamp of event in local time zone. Local time zone is set in user s profile in MobileFabric console by Kony, Inc. All rights reserved 89 of 124

90 47. Session TimeStamp_UTC Time stamp of session init in UTC 48. Session TimeStamp_Local Time stamp of session init in local time zone. Local time zone is set in user s profile in MobileFabric console. 49. Request TimeStamp_UTC Time stamp of service request in UTC 50. Request TimeStamp_Local Time stamp of service request in local time zone. Local time zone is set in user s profile in MobileFabric console. 51. Request MobileFabric app guid application guid generated on creation of an app in MobileFabric console. 52. Request MobileFabric app name application name provided on creation of an app in MobileFabric console. 53. Session MobileFabric app guid application guid generated on creation of an app in MobileFabric console. 54. Session MobileFabric app guid application name provided on creation of an app in MobileFabric console. 55. Object method Type of the object method ex. PUT, POST. Applicable for services with object mapping. 56. Object name Name of the object that is mapped in service request. Applicable for services with object mapping. 57. Integration service version header Version of the integration service requested by application in the service request header. 58. Integration service version Version of the integration service served by the application server for a service request. Measures: 1. Internal Duration - Time spent by the service call in Kony App Services for internal processing 2015 by Kony, Inc. All rights reserved 90 of 124

91 2. External Duration - Time spent by the service call in Kony App Services for external call from Kony Server to backend 3. PostProcessor Duration - Time spent by the service call in Kony app services in custom post-processing logic in the service 4. PreProcessor Duration - Time spent by the service call in Kony app services in custom pre-processing logic in the service 5. Parse Duration - Time spent by the service call in Kony app services in parsing response from external source 6. Total Duration - Total time spent in Kony app services server for the service call, from the time request was received by the server until the response was sent back to device. Total duration is equal to the sum of all the duration fields. 7. Error Line Line number in application code file where error occurred. Applicable for event types error/exception. 8. HTTP Response Code HTTP code of the service response obtained by the device. 9. Response Time Response time as viewed by the client device. That is time since service request is sent from device to server and response obtained back in the device. 10. Event Session Key Unique session identifier for the session in which the application event occurred. 11. Middleware Session Key Unique session identifier for application session data from session init call. 12. Object mapping duration (request) Time taken to map the object detail into service request by Kony app services. 13. Object mapping duration (response) Time taken to map the object detail into service response by Kony app services by Kony, Inc. All rights reserved 91 of 124

92 14. Count Sample custom field created to show count of application. This is to function as a count(*) for application session and service request calls. Note: Similar data is sometimes made available for different types of data like Events, Session, Service Requests, Error as data is stored in different tables for them and having different fields called out enables a more optimized query to run if only one type of network call is used in a custom report. Note: All duration fields indicate time duration in milli seconds. b. The domain has data of all service calls made to this application and all custom metrics that were sent. Note: To view only Custom Metrics service-related data for an application, add a prefilter or filter while creating reports for Service ID equals "capturekonycustommetrics." 10. Click Choose Data. The Data Chooser dialog appears by Kony, Inc. All rights reserved 92 of 124

93 11. Select items from the Source pane and move them to the Selected Fields pane. a. Click Add to move an item from Source pane to Selected Fields pane. b. To move all the items from Source pane to Selected Fields pane, click Add All icon. c. To remove the items from Selected Pane, select an item from the Selected Fields pane and click Remove icon. d. To move all the items from Selected Fields pane to Source pane, click Remove All icon. 12. Select items from the Source pane and move them to the Selected Fields pane. a. Click Add to move an item from Source pane to Selected Fields pane. b. To move all the items from Source pane to Selected Fields pane, click Add All icon. c. To remove the items from Selected Pane, select an item from the Selected Fields pane and click Remove icon. d. To move all the items from Selected Fields pane to Source pane, click Remove All icon by Kony, Inc. All rights reserved 93 of 124

94 Note: Selecting display fields in the Fields screen is a mandatory step. 13. Click Pre-filters. This is an optional setting, if you want to restrict data available to the report builder. a. To add a Pre-filter, double-click a field from Fields pane. The field is added to the Filters pane, and you can configure options to customize the filter. For example, if you want to view only the data of custom metrics services, and not view data of other service calls for the same application, create a filter for Service ID. Next choose a function as equals, choose capturekonycustommetrics from the list, and configure it. b. Click Locked check box to make the pre-filter unchangeable within the report builder. Important: Do not use this option if you want the filter value to be editable from the report builder (Ad Hoc view) by Kony, Inc. All rights reserved 94 of 124

95 c. The following image shows a filter added to the Filters pane. d. Select a criteria from the list. By default, equals is selected. The following options are available: 2015 by Kony, Inc. All rights reserved 95 of 124

96 e. Search for the type by entering a keyword in the box and click Search. The type of the item is based on the selected pre-filter. f. You can also select the type from the list. The list is populated with all the values of the selected pre-filter. In the current example, the list is populated with all the types of channels. 14. Click Pre-filters. This is an optional setting, if you want to restrict data available to the report builder. a. To add a Pre-filter, double-click a field from Fields pane. The field is added to the Filters pane, and you can configure options to customize the filter. For example, if you want to view only the data of custom metrics services, and not view data of other service calls for the same application, create a filter for Service ID. Next choose a function as equals, choose capturekonycustommetrics from the list, and configure it. b. Click Locked check box to make the pre-filter unchangeable within the report builder by Kony, Inc. All rights reserved 96 of 124

97 Important: Do not use this option if you want the filter value to be editable from the report builder (Ad Hoc view). c. The following image shows a filter added to the Filters pane by Kony, Inc. All rights reserved 97 of 124

98 d. Select a criteria from the list. By default, equals is selected. The following options are available: e. Search for the type by entering a keyword in the box and click Search. The type of the item is based on the selected pre-filter. f. You can also select the type from the list. The list is populated with all the values of the selected pre-filter. In the current example, the list is populated with all the types of channels. 15. Click Pre-filters. This is an optional setting, if you want to restrict data available to the report builder. a. To add a Pre-filter, double-click a field from Fields pane. The field is added to the Filters pane, and you can configure options to customize the filter. For example, if you want to view only the data of custom metrics services, and not view data of other service calls for the same application, create a filter for Service ID. Next choose a function as equals, choose capturekonycustommetrics from the list, and configure it by Kony, Inc. All rights reserved 98 of 124

99 b. Click Locked check box to make the pre-filter unchangeable within the report builder. Important: Do not use this option if you want the filter value to be editable from the report builder (Ad Hoc view). c. The following image shows a filter added to the Filters pane by Kony, Inc. All rights reserved 99 of 124

100 d. Select a criteria from the list. By default, equals is selected. The following options are available: e. Search for the type by entering a keyword in the box and click Search. The type of the item is based on the selected pre-filter. f. You can also select the type from the list. The list is populated with all the values of the selected pre-filter. In the current example, the list is populated with all the types of channels by Kony, Inc. All rights reserved 100 of 124

101 16. Click OK. The filter is added to the Data Chooser. You can modify or remove the filter by clicking on Change or Remove links. 17. Click Display. The following screen appears. In this screen, you can change the display name for fields, re-order, and pick the list type by Kony, Inc. All rights reserved 101 of 124

102 a. Click a Display Label and an editable box appears. b. Enter a name for the display label. c. Move the fields up or down using the Move Up and Move Down options. d. Move multiple fields to top or bottom using the Move to Top and Move to Bottom options. 18. To generate a report, select an option from the following list. The Data Chooser dialog provides three options to generate the report: a. Click Table to generate a table report. A report builder screen appears in which you can customize the view of the report with Fields and Measures. To view the user interface elements of a table report, click here. b. Click Chart to generate a chart report. There are different kinds of chart reports available in cloud portal. To view the user interface elements of a chart report, click here. c. Click Crosstab to generate a cross tabulation report, which allows you to do cumulative operations like total and sum. To view the user interface elements of a crosstab report, click here. d. Click Cancel to close the Data Chooser dialog by Kony, Inc. All rights reserved 102 of 124

103 Note: The options for choosing Table, Chart, Crosstab from this menu is only available in Jaspersoft 5.6 version for on-premises. For Kony Cloud the default data view type is crosstab. User can change it to any format after the report builder user interface gets loaded. The Default Ad Hoc View for Table report is illustrated in the following picture: Two types of items appear in the New Ad Hoc View dialog to the left: a. Fields - Non-numeric value will be in the field. b. Measures - Measurable field. Any value like long or double will come as a measure Table Report User Interface The following picture illustrates a table report and the options in the Report Builder (Ad Hoc Editor) by Kony, Inc. All rights reserved 103 of 124

104 The Report Builder screen displays the following items: 1. Data Selection panel - The Data Selection panel shows the list of available fields, which can be added to any bar in the Layout Band, and measures, which are summarized values that cannot be added as groups. Typically, measures are created from numeric fields in the Topic or Domain, but in some circumstances, it makes sense to use string fields when summarized as a count. For example, you might want to display the number of unique customers that made purchases in a given quarter. Use the icon beside the set name to expand or collapse a set of fields or measures. To hide this panel, click the icon in the top left corner; click the same icon on the minimized panel to expand it. a. Change source / Select fields - This menu allows you to select a different Topic or Domain for your view. All data and formatting are lost when you select a different Topic or Domain. When creating a view from a Domain, you can also select different fields to change the list that appears in this panel. 2. Tool bar - The tool bar at the top of the canvas provides access to many of the Ad Hoc Editor s functions, such as saving the view or creating a report from the view, undoing and redoing changes, and changing the view s sort order. 3. Data mode menu - Click to select the amount of data displayed from the menu. Use Sample 2015 by Kony, Inc. All rights reserved 104 of 124

105 Data to design a view more quickly, or use Full Data to see all your data used in the same view. When you choose display mode, full data is displayed regardless of the selection shown in the editor. Note: Using Full Data option might decrease the performance of the report. 4. View type menu - Click Chart, Table, or Crosstab to see your data in that type of view. The changes made in one type of view apply to the data displayed in another. 5. Title bar - The top portion of the canvas; click to add or edit the title of the view. To remove the title, point to the Properties menu and select Toggle the Title Bar. 6. Layout Band - The layout band immediately below the toolbar has two boxes where you can drag and drop fields and measures from the Data Selection panel to add them to the canvas. You can change the order of the selected field's canvas by dragging them to a different location in the layout band. The boxes have different labels and functions, depending on the type of view. To hide the layout band, click on the Properties menu and select Hide Layout Band. a. Columns area - Drag fields and measures from the Data Selection panel to this area to create columns. b. Groups area - Drag fields from the Data Selection panel to this area to create groups. The Measures cannot be added to the Groups area. 7. Canvas/Report Builder Area - Occupies the middle area of the editor. The canvas shows your data subject to the constraints you have created. This is also a sample of how your data will appear in any report you create from the view. To see the view without interface components, click Toggle for design mode. 8. Filters Panel / Filter Controls - These menus allows you to change the display of filters, either collectively or individually. The menu on the filter panel allows you to collapse all filters or remove all filters. To minimize the view of an individual filter, click the icon beside its name. This panel displays any filters defined for the view. You can set the filter values, and see the resulting 2015 by Kony, Inc. All rights reserved 105 of 124

106 change in the canvas. To hide the Filters panel, click the icon in the top left corner of the panel. Click the same icon on the minimized panel to expand it again Chart Report User Interface The following figure illustrates the Canvas or Report Builder area in the Ad Hoc Editor. Sliders in the Filters pane are also shown: 1. Chart Type - Allows you to modify the selected chart type. As Chart is selected, the chart type of a report is displayed in the Report Builder area. 2. Canvas Options - Allows you to select different chart types and chart formats by Kony, Inc. All rights reserved 106 of 124

107 a. Click Chart Types.. option. The following dialog appears. Click to select a chart type. A blue border indicates the current selection. 3. Scale - All measures are plotted against the same scale, which is sometimes confusing. You can use a calculated field to multiply or divide one measure so that its values are closer to those in the other measures in your chart. 4. Legend - The legend is created when measures are added to the chart. Click one or more legends to hide the associated measures; click again to show them. 5. Labels - The labels on the horizontal scale indicate the values by which the chart is grouped. If there are too many values in the chart, zoom in or use filters to reduce your data. 6. Slider - Drag to set the level of aggregation to use for viewing the data. 7. Report Title - This allows you to enter a report title by Kony, Inc. All rights reserved 107 of 124

108 Note: As the nature of a chart is to display summarized data, the data mode menu is not available. Charts always present the full data set, not a sample. This may impact performance when working with large data sets. In addition to generating a chart, you can also do the following: 1. Zoom - Click and drag or swipe to zoom. Only labels used in the zoom area are displayed, so you can use zoom to simplify your view. The zoom level is not saved when you save a view or report; it is always reset to the full view of the chart. A Reset Zoom option appears if you zoom to reset the zooming level to normal. 2. Filter a Chart - Right-click a field in the Data Selection panel or the layout band and select Create Filter. or 3. Select a measure s summary function - Right-click the measure s name in the layout band, and select a function from the context menu by Kony, Inc. All rights reserved 108 of 124

109 4. Set the granularity of groups - Use the slider to set the granularity of groups Crosstab Report User Interface The following picture illustrates a Crosstab Report in the Ad Hoc editor. Note: It is recommended to work only with Sample Data while building reports. Columns Area - Drag dimensions and measures from the Data Selection panel to this area to create column groups. Drag fields to change the order of the groups. The Measures must all be in the same area. You cannot have measures in the Columns and Row areas at the same time by Kony, Inc. All rights reserved 109 of 124

110 Rows Area - Drag dimensions and measures from the Data Selection panel to this area to create row groups. Drag fields to change the order of the groups. Measures must all be in the same area. You cannot have measures in the Columns and Row areas at the same time. Row and Column group labels - This displays the name of each field used for grouping. Right-click the group labels to use the context menu. When no row groups are defined, the words Row Group indicate this vertical region. Row and Column group values - These values are heading cells that show the group values. When there is more than one level of grouping, use the icons on the outer groups to expand or collapse the inner groups. Right-click a group value to exclude it or to keep only that value from among all group values of the same level. Additional actions you can perform while working with Crosstab Report. Set the granularity of date groups - When you select a date field as a group, you can specify the granularity of the group values. Right-click the group label, select Change Grouping, and select Year, Quarter, Month, or Day. Pivot a single group - To pivot any group from row to column or row, select the group by clicking its label, and then drag it to the other area. You can also right-click the group label and select Move to Column Group for row groups or Move to Row Group for the column groups. Pivot entire crosstab - To pivot all row groups to column groups at the same time, click Switch the groups icon. Filtering - Right-click a group label and select Create Filter to filter your data by the members in that group. Note that creating a filter from a group is very similar to slicing. Keep Only - Slice out a single group by right-clicking its group value and selecting Keep Only. Use Ctrl-click to select multiple members to keep. Exclude - Remove a group value from any group by right-clicking it and selecting Exclude. Use Ctrl-click to select multiple members to exclude. Summaries (Totals) - By default, the crosstab includes grand totals of all row groups, shown in a Totals row at the bottom, and of all column groups, shown in a Totals column to the right by Kony, Inc. All rights reserved 110 of 124

111 To toggle the row totals, right-click the left-most row group and select Delete Row Summary or Add Row Summary. To toggle the column totals, right-click the topmost column group and select Delete Column Summary or Add Column Summary. You cannot hide the inner totals of an expanded row or column group. Change Summary Functions - Right-click a measure label and click Change Summary Function to select a summary function. For example, you may want to display an average rather than a total. Column group limits - In some cases, the editor prompts you to confirm that you want it to return large amounts of data. When the number of column groups exceeds a configurable limit, the editor displays an ellipsis (...); its ToolTip indicates the number of remaining groups. Click the ellipsis to display them. Sorting - Crosstabs support multiple levels of sorting: Right-click Measures to sort measure groups by label. Right-click a row or group label to sort its values. When your selection contains inner groups, they are also sorted. Right-click an inmost column header to sort the column values. Sorting can only be set for one column at a time. 4.2 Saving Custom Reports and Ad Hoc Views 1. You can save custom reports from the report builder screen. 2. In the Report Builder screen, click Save option. The following options appear by Kony, Inc. All rights reserved 111 of 124

112 3. Click Save Ad Hoc View and Create Report option to save the Ad Hoc view and Create a Report. The following dialog appears. To save an Ad Hoc view and create a Custom Report, follow these steps: 1. You can configure the Data View Name and Report Name. 2. Enter a data view description and report description in respective text fields by Kony, Inc. All rights reserved 112 of 124

113 3. Select a folder where you want to save the data view and the report name. 4. Select a template from the Generate Report with area. 5. Click Save. After saving the report, you can access it from the respective folders (Shared/Private). Note: To close the report builder screen after saving the report, click X in the top right corner. Ensure you save your work before exiting the report builder. Any unsaved work will be lost. Note: Reports and Ad Hoc Views saved in Private folder are accessible only for the user that created the Private folder. Save the reports in Shared folder to be used by other users of the account that have report viewing permissions. 4.3 Running Custom Reports After you have saved your custom reports, you can run them from the Custom Reports screen. Ensure that you have saved the report in Shared or Private folder. You can run custom reports from the Custom Reports screen. For this you need to have created and saved the Report and Ad Hoc view by Kony, Inc. All rights reserved 113 of 124

114 1. Click Custom Reports in the left-pane, the following screen appears. 2. Select one of the folders. You can select Shared or Private folder by clicking on the respective buttons. 3. Select a report and click Run. 4. If report has filters a popup will be shown as shown below with the filters (input params) by Kony, Inc. All rights reserved 114 of 124

115 5. Clicking on a filter opens the appropriate type of input. a. A drop-down list is provided for selecting string. b. A text box is provided for numeric values. c. A calendar is provided for Timestamp values. d. Click Generate after setting the filters to generate the report. 6. If the report has no filters defined, clicking on run will directly generate the report shown below by Kony, Inc. All rights reserved 115 of 124

116 a. A user can click on refine reports to modify the input parameters (Filters) and rerun the report. b. Export to option allows a user to export the report to a pdf. 7. To delete a report, select a report and click Delete. This action cannot be undone. 4.4 Editing Ad Hoc Views After you have saved the Ad Hoc Views, you can edit the report and modify the parameters linked to the report. Follow these steps to edit the Ad Hoc Views by Kony, Inc. All rights reserved 116 of 124

117 1. When you Click Ad Hoc Views tab, the following screen appears. 2. Select a report from Shared or Private folder. 3. Click Edit. The Ad Hoc View screen appears. 4. In this screen, you can edit the report by adding new columns or groups or configuring filters for the data. 5. After you have made changes, save the report by Kony, Inc. All rights reserved 117 of 124

118 6. To delete an Ad Hoc View, click the view and select Delete. Note: Ad Hoc views with dependent reports cannot be deleted, before deleting the dependent reports. Note: Modifying the Ad Hoc View will affect reports dependent on it. Some changes like adding new filters will get reflected on existing dependent reports. Changes like adding new columns will not reflect on any existing report that was built with this Ad Hoc View. It is recommended that if you modify an Ad Hoc View that has reports built from it, save the report under a different name. 4.5 Advanced Actions in Custom Reports You can do the following advanced actions in the Custom Reports screen. 1. Using Filters 2. Changing Data Format 3. Creating Custom Fields Using Filters You can use filters to configure the custom report being built by Kony, Inc. All rights reserved 118 of 124

119 1. Right-click an item in the Domain panel and click Create Filter. The filter appears in the Filters pane. 2. Use the fields in the filter to change its value. 3. While using multiple filters, you can build expressions for applying filters using AND, OR and NOT operators. o When all filter conditions must be true, use AND. For example: A and B and C. o When any one of the filter conditions must be true, use OR. For example: A or B or C. o When one of the conditions has to be not true, use NOT. For example: not A by Kony, Inc. All rights reserved 119 of 124

120 o You can use a combination of these as well. For example: (A and B ) or C. 4. As you set the filters in the Filters pane, the data is filtered and appears in the Canvas/Report Builder area Changing Data Format While creating a report, you can modify the data format of fields like Date, Timestamp. After you add fields as Columns or Groups, you can right-click on the table/crosstab data and select Change Data Format. The following picture shows Change Data Format option for a table report by Kony, Inc. All rights reserved 120 of 124

121 The following picture shows Change Data Format option for a Crosstab report by Kony, Inc. All rights reserved 121 of 124