TEL_BOT release v2.1.0

COMUNICADO DE ATUALIZAÇÃO DO CHATBOT

Adicionado sistema de envio de fatura de forma assíncrona.

Agora, o chatbot irá realizar os processos de obtenção de faturas e envio separadamente:

1. Primeiramente, ele atenderá à equipe e realizará a solicitação da fatura;
2. Outro agente aguardará pela fatura e enviará quando ela estiver pronta;
3. Isso liberará a fila para outras solicitações, reduzindo o tempo de espera.

Ainda estaremos dependentes do sistema SAP, mas isso reduzirá muito o tempo de espera por faturas!

Versão atual: 2.1.0

TEL_BOT release v2.0.4

COMUNICADO DE ATUALIZAÇÃO DO CHATBOT

1. Realizado balanceamento das instâncias que atendem solicitações normais para as instâncias que atendem solicitações de fatura;
2. Melhorado as definições de armazenamento de logs, criando logs diários, facilitando a detecção de problemas e erros.

Versão atual: 2.0.4

TEL_BOT release v2.0.3

COMUNICADO DE ATUALIZAÇÃO DO CHATBOT

Resolvido alguns bugs.

Versão atual: 2.0.3

TEL_BOT release v2.0.2

COMUNICADO DE ATUALIZAÇÃO DO CHATBOT

Agora as solicitações de fatura serão atendidas separadamente!

Devido as quedas e lentidões frequentes no sistema de faturas da Light, as solicitações estavam ficando atrasadas, mesmo as que não tem relação com as faturas.

Agora que elas serão atendidas separadamente, mesmo que o sistema de faturas da Light caia, as outras solicitações serão atendidas normalmente, eliminando assim, o atraso no atendimento.

Versão atual: 2.0.2

Chatbot v2.0.1

Fixed issues with sending invoices:

In the update to version 2.0.0, the instruction to clean the temporary folder was removed, due to simultaneous invoice requests, it could delete invoices still pending to be sent.

An instruction was inserted in the temporary folder scanning function to delete invoices marked as sent, but it was not being executed, resulting in the accumulation of invoices in the temporary folder.

The accumulation of invoices added time to scanning the folder, to the point where requests expired before the invoices were even sent, causing further accumulation.

To solve the problem, a function was added to delete invoices immediately after sending instead of marking them for deletion.

Chatbot 2.0

Added asynchronous service functionality for the appropriate number of instances, informed by the '--sap-instancia' parameter.

• Added abstractions, still in progress;
• Migrated SQLite database to PostgreSQL;
• Fixed some known issues;
• Removed many deprecated methods;
• Refactored most codes;

chatbot v1.9.0

Added #InvoicePRL subsystem for sending invoices through the SAP NetWeaver PRL module.

The subsystem comes as an alternative for sending invoices if the SAP FrontEnd system is not generating PDFs or there is no registration with an invoice printing profile.

As the system is via the web, it uses an instance of the Google Chrome browser to interact with the system interface, and due to this, it will not be possible to use the #BlackMouth subsystem, as it also uses an instance of the browser, causing conflicts.

This system is not intended to replace SAP FrontEnd, but rather to provide a temporary alternative for sending invoices'

chatbot v1.8.0

The following corrections and improvements were made:

• #crossover functionality for expiration and flag reports for more than one region;
• Reports from the #blackmouth subsystem will be transmitted via Telegram channel, for each service lever, keeping the chatbot's chat window clean;
• Improvements to the #blackmouth subsystem:
  • More user-friendly final report;
  • Automatic day change;
  • Exception for inactive teams;

chatbot v1.7.0

The following corrections and improvements were made:

• Problems in the OFS subsystem have been fixed;
• Changed the way to start subsystems;
• Added internal repetition, error handling and specific waits for each advertiser;
• Fixed problems in assigning the 'controller' role to receive advertisements;
• Added verification and automatic restart of the OFS monitor subsystem;
• Added submission of OFS final analysis report;

chatbot v1.8.0b

IDG Offending Team Monitoring System

The system aims to monitor and warn as quickly as possible about teams that are offending the IDG as per analysis of the data provided by the client's OFS system.

Monitoring is carried out through a scraper in the client's OFS system, where information about the IDG situation is obtained.

The ofs.conf file must be configured:

• GCHROME: path to the Chrome executable;
• WEBSITE: path to the client's OFS system;
• USER: the registered user with permission for WFM;
• WORD: the password of the user entered above for the system;
• RESOURCE: bucket of resources to be monitored.

The monitor system must be run separately with the slower argument for slow scenarios