Creation of Messages Reporting Table
We have hit the upper limits of running month-long reports for detailed message data and aggregated counts using our current database architecture. To improve the runtime and performance of many of our most expensive reporting queries, we stood up a new data table that is populated with data by events, including adding some important information to record in the new table that will eliminate our need to join across other tables and do calculations in the queries.
In this release, we stood up the new table, backfilled the data for a few months, and have moved our Big Number Stats query (the calls hit when people load the homepage of our platform) to use this new data table. In the coming weeks, we will be moving many of our other reports to hit this new table instead of our live tables.
Optimized Our Internal Reporting for Nice Billing
As a symptom of the problem described above, we were encountering timeout issues with our monthly billing reports that get sent to Nice. Because of the amount of the data and how it was being pulled, it was timing out prior to being able to send it through the API request.
The team made a large number of optimizations to this query and underlying calls to get it to run in about 2 minutes. This is part of what prompted us to do the work to create a reporting specific data table. In the next few weeks, we will actually be migrating these reports to use the new data table and they should run in seconds.
v1 Migration Tool Progress
We are continuing to make progress on our v1 Migration tool. This is a tool that is designed to allow us to move the lines, messages, and conversation data for a client on our v1 platform over to our v2 platform. In this release, we are releasing the component that migrates over the Customer Lines.
Platform API | Swagger Documentation Throwing 500 Error
As we get ready for joint work integrating Conversation Inbox and Campaigns inside of the Capacity UI, we needed to make sure the broader Engineering team had good documentation on the Textel Platform API, which is the API that the Textel UI uses to power the interface. Swagger is an API documentation tool that automatically creates the documentation, but we had a few issues that were causing it to error out. Those will be resolved in this release.
Bug Fixes
CRUDy | Only call GET Guided Conversations on a Line if it is Bot Enabled
Implement a forced wrap on messages when long links or long unbroken text is sent (to or from) the platform
RingCentral | OutgoingProcessor - External group chat is not found
Internal API | Message Usage Report Fixes