Kubes - Analytical Cubes
Kubes represents the data organized in DataKubes; it is the synonym for Data Cubes.
In DataKubes, it is allowed to create Kubes to data stored in repositories, DataStore repositories only.
Kubes are the basis for creating Dashboards and enrich the DataKubes data search engine.
Creating a Kube
To create a Kube, you have to go to Kube Designer> Create Kube. Then, the following screen will open:
Just fill in the data, and once ready, click "Save." Once the system is prepared, it will redirect you to the Kubes Designer.
The Kubes designer allows you to configure the Kubes in DataKubes. Here's an example of the designer's screen:
This Kube represents the customer's list in the "InterFuerza ERP" data source.
Description of the Tabs in the Designer:
|Properties||This section defines the name, the data source connection, and the Kube description.|
|Options||This tab defines the predefined options when the Kube is used, for example, what visual format you want, the number of lines, and others.|
|Charts||In this tab, the primary Kube chart is defined, and it is allowed to associate other charts with their respective keys. Thus, it would be the charts part in an SQL statement, for example.|
|Fields||In this tab, the desired fields to present in the Kube are added. These fields can be of two types:|
Table Field , which is a field of the associated tables in the chart tab.
SQL field this field allows you to place an SQL code that returns one value which is extremely powerful to feed your Kube with data mining.
|Predefine Values||In this tab, you configure the visible columns, groupers if required, and the detailed parameters of the different visualizations that DataKubes has.|
|Filters and Sorting||This tab defines the predefined session and date filters you want to run at startup when the Kube is used. In addition to the desired ordering.|
|Data Relationship||This section defines the metadata to enrich the analytical search of DataKubes. Here you can relate the Kube data in design with other existing Kubes in DataKubes.|
|Users||In this tab, you can provide access to users who can use the Kube from the web environment and mobile apps.|
Remember that to create dashboards and use DataKubes visual search, you need to configure Kubes in your account.
En propiedades se configura la conexión del Kube, además de nombre y otros valores descriptivos del Kube.
The options configure specific parameters that are predefined at the time of running for the first time.
|Initial Visual Format||Defines the report format when it is loaded for the first time in the viewer.|
|Number of Lines||Number of lines to show in detail. This only applies to Detailing without grouping.|
|Totalizer Types||It defines if it should show the totalizer at the end of each group and the end of the report with the grand total.|
This section configures the tables that make up the Kube. You can define multiple charts, and their relationship braces can be defined:
Keys of Relation
Remember to place at least one relational key; however, DataKubes allows you to relate charts without a key to obtain a result for each value found in each chart.
In this tab, the fields that make up the Kube are defined; you can define multiple types of options in this tab.
There are two types of fields, the Chart field, which brings the listed columns of the charts in the previous tab, and the SQL type field, which allows you to place an SQL code to give value to the column.
|Numeric||It will format the value with the sign of thousands and decimals up to 2 places.|
|Date||The value will be treated as a date, it will allow enabling the TimeSeries in the graphs.|
|Percentage||The value will be treated as a percentage and converted x 100, and the% sign added as a suffix to the value.|
|The value will be treated as email, allowing to add a menu to send an email with the predefined client in the user and open the Social Scan (if it is integrated)|
|Image||The value will be treated as containing a URL to an image and added as a Thumbnail in detailed reports and other places in DataKubes.|
|Geo POINT||It will treat the value as containing the geographical coordinates of the record, and it must include Longitude, Latitude for example.|
Remember Recharge as you change fields
Currently, the DataKubes Kubes designer needs to be re-loaded to load the report fields in the different necessary options, for which we recommend pressing the "Reload Fields" button when making changes.
This section allows you to configure the predefined values when running the report in the different ways to view it.
Each type of report allows you to define how you want it to be pre-configured when users use it.
Filter & Sorting
In this section, you can configure the predefined filters that can be configured at the time of use,
*Filtro de Fecha
Este filtro habilita o no en el visor el filtro por rango de fecha, el cual es útil para segmentar los resultados analizados por un tiempo determinado.
Grupos de Filtros
Estos grupos son la estructura más alta de los filtros utilizados en DataKubes, el grupo puede ser considerado como el "( )" dentro de los WHERE de un SQL. Esto permite crear grupos de filtros complejos.
Tipo de Filtro
You can add different types of filters. Currently, DK allows Se pueden agregar filtros de diferentes tipos, actualmente DK permite filtro normal que compara de campo a valor, campo contra una lista de valores y campo contra otro campo.
Field Filter vs Field
Remember that adding a filter that compares the field against the same field causes all the values to be considered equal. Thus, generating a kind of 1 = 1.
The Sorting allows adding multiple levels that the report requires to order when it is first generated. Currently, it allows Ascending and Descending sorting.
Data Relation (Searching)
This section defines the users who can use this Kube. You can select multiple users to add, and you can remove users that you do not want to enable the Kube to.
The system will add the user creator of the Kube every time a new Kube is created.
User Management and its Kubes
In this segment, you can add multiple users to the Kube being designed. In addition, however, you can control all the Kubes that a user can access by entering the user manager and selecting permits.
In DataKubes, there is the possibility of creating indicators to show relevant data, which are very useful in DashBoards and to show relevant and unique information.
Currently, we show some examples:
Creating an Indicator Card
To create a card, proceed to the Kubes designer and place create a new Kube,
Then select the option for Type * Card .
Once the card is created, it will appear in the Kubes list with the Gauge icon as shown in the following image:
Configuring Indicator Cards.
Indicator cards work with a value and a goal. This allows you to create powerful indicators based on these two values.
The value of the goal is optional.
Here we explain the Card designer:
The properties define the name, category, main repository, and description of the card.
The Card Configuration allows being able to establish the values and the design of the card.
Description of the screen property as follows:
|Title||Title to show when viewing the card.|
|Font Size||The desired size for the gauge currently allows "Large, Medium, Small."|
|Icon Types||The icon you want to use to decorate the card can be any value from the Awesome Font Library, [https://fontawesome.com/icons?d=gallery)(https://fontawesome.com/icons?d=gallery )|
|Visual Type||Allows you to define the layout, if it is a normal indicator or if it is using the graphics engine.|
|Date Range||This option allows you to define if the indicator uses the date filter.|
The Card Icon allows you to give an additional decoration to the card indicators.
You can choose icons from the icon gallery of the Awesome Font.
The basis of every card is the value parameter, it is obtained by defining an SQL in the "SQL Value" section, which must always bring a value as a result, and only the first row of the result will be used.
The value parameter can be defined from which source connection its value is obtained, the type of data that allows the value to be formatted, and the CSS Class to which the indicator is applied. For example, in the following configuration:
The result will result in the following card (Using our DEMO)
The Goal is optional.
Remember to set Visual Type to show with or without a goal.
The parameter works similarly to the value parameter but defines the benchmark goal for the value parameter.
For example, using the following configuration:
Which will result in the following card:
This card shows us that we have 83 thousand vs. the goal of 100 thousand. It is beneficial for displaying these types of indicators.
CSS class defines the color of the indicator text.
This option allows to define the text of primary color, green, yellow, red, or automatic, which depending on if the value is (+) will show green, (0) will show yellow, and (-) in red.
To apply the range dates used in the viewer, you can use the texts:
DATEFILTER-FROM # for Date From
DATEFILTER-TO # for Dates Up
They can use them as many times as necessary and in both the value and goal parameters. The SQL code must use it between single quotation marks since when the card is generated, it only replaces the value of the dates without adding quotation marks.
Updated about 1 year ago