Fluig has an advanced Analytics feature, which enables the creation of Dashboards and Views for monitoring information indicators that occur within the Fluig platform. This service is available in cloud only, which ensures that the entire broad processing of new information and data analysis occurs with great scalability.
To enable Analytics in your environment, the following steps should be followed.
Open a call via the Customer Portal in "Calls > Software > Fluig" using the following parameters:
Version |
Fluig |
Module/Product |
Fluig |
Process or Routine |
Analytics |
Summary |
Creating project Analytics |
Incident |
Information for creating context:
|
As a result of the call, two environments will be
released: one for production and the other for testing, in which
the administrator will receive an e-mail invitation to participate
in the Analytics project, and will receive, in the call, the codes
of the projects created.
In the environment with Fluig that you want to connect the integration with Analytics, you will need to access the WCM administrator environment (with the WCMAdmin user). In this environment, go to:
- Menu option: Control panel
- Click on the WCM tab
- then go to the Companies option
In this option, select the company you want to enable Analytics, then click Edit. Then go to Register additional data and on the following screen add the following keys and values
Key |
Value |
analytics.gd.project.id |
<your project code sent by support> |
analytics.gd.user |
<e-mail in which you received the invitation from support> |
analytics.gd.pass |
<password registered after the invitation> |
analytics.gd.active |
true |
With the invitation received by mail, complete your registration on Fluig Analytics. With this user and password, you will be able to monitor the data being sent.
Sending Data
Data is sent in regular intervals of 15 minutes. Only data that has changed over this period is sent. Communication is always made from the server to analytics.fluig.com. The firewall must be disabled for this address.
To send specific Workflow processes data, the event beforeSendData must be used for configuration of the data sent to Analytics.
The function to treat this process event has two parameters customField and customFact. The first parameter is an array of strings already instantiated, with 10 positions (0 to 9). The second parameter is an array of 10 positions, but the data must be double type and its content will be treated as a "fact". The big difference between a customField and a customFact field is that in a fact field (customFact), as it is a number, operations such as sum, average, maximum and minimum can be calculated. These are some examples of field types and the value that should read:
Field | Field to be sent | Justification |
---|---|---|
Purchase order region | customField | Since the goal is to tell in which regions the applications were requested, it doesn’t have to be a fact field. |
Requester name | customField | It will only be used as a cluster |
Total order amount | customFact | To retrieve information such as average order amount of a region |
Number of items in order | customFact | Add up how many items were requested by a requester |
Below is a sample implementation of the event, with two fields filled out:
function beforeSendData(customField, customFact) { customField[0] ="1"; customField[1] =hAPI.getCardValue("campo_do_formulario"); customFact[0]=10.53; customFact[1]=java.lang.Double.parseDouble(hAPI.getCardValue("campo_valor")); }