TOTVS Fluig English

Árvore de páginas

Versões comparadas

Versão antiga 3

changes.mady.by.user Igor Duquia Giumelli

Gravado em

comparado com

Nova versão Atual

changes.mady.by.user Denise De Deus

Gravado em

Chave

  • Esta linha foi adicionada.
  • Esta linha foi removida.
  • A formatação mudou.

...

Deck of Cards
idenable-analytics-steps
Card
defaulttrue
id1
labelStep 1

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:

  1. Company Name
  2. CNPJ (Corporate Taxpayer's Registry)
  3. TOTVS customer code
  4. Code of context to be created (usually company name, may contain space, characters without diacritics and numbers) 
  5. Administrator’s name and last name
  6. Analytics environment administrator’s e-mail

 


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.

 


Card
id2
labelStep 2

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:

  1.  Menu option: Control panel
  2. Click on the WCM tab
  3. 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

Card
id3
labelStep 3

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.

Aviso
titleWarning

Do not disclose your project code, this is the key to access to your project.

...


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.

...

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:

FieldField to be sentJustification
Number of items in ordercustomFactAdd up how many items were requested by a requester 
Purchase order regioncustomFieldSince the goal is to tell in which regions the applications were requested, it doesn’t have to be a fact field.
Requester namecustomFieldIt will only be used as a cluster
Total order amountcustomFactTo retrieve information such as average order amount of a region

Below is a sample implementation of the event, with two fields filled out:

...