Embedded Files
Textel Platform Updates
Textel Platform Updates
Account Manager Tool (CRUDy) Updates
We have added another enhancement to make using the tool a bit easier as well as beginning the steps to tie our internal systems together a little more.
Persistent Filters - On many pages, you have the ability to filter the data. The issue was that those filters were not sticky and did not persist. So as an example, if you filtered down to only see lines from one account and then clicked in to one of the detail pages of the line, when you would go back to the lines page, your account filter would be removed, causing you to reapply the filter. We have changed this so that your applied filters stick until you remove them as well as made applying filters a bit more user friendly.
Salesforce ID Field on Accounts - In preparation of sending billing reports over to Salesforce for clients on our new platform, we needed a way to tie accounts together between the two systems. Now on the Account page in CRUDy, we have added a Salesforce Account Id field. This should be populated with the Id for that account from Salesforce, specifically the full account ID from the URL in Salesforce.
Public API Updates - New Blast API Call
SEARCH Blast Campaigns - We now have an API call that allows you to search and find campaigns within your account. We provide a variety of ways to filter the campaigns to get results back including outbound line, start/end date, status, etc.
Platform Health Updates
Expanded Unit Test Coverage
Report Repository & Service
Messaging Business Texting Service
Moved Conversations API Into Platform API Code - This consolidation will help avoid duplication.
Reporting Inconsistencies Between Reports - Since our reports were built by different people at different times, there were some inconsistencies in column naming conventions, line selection dropdowns and other things that we cleaned up.
Reporting Updates
Conversation History Report Now Reports on Message Authorship - In the last few sprints, we did some work to update our system so that we record which user/agent actually authored a message sent in a conversation. Prior to this, we instead supplied the user/agent who had the conversation claimed. However, in our platform, users can contribute to a conversation even if they do not have it claimed. So to make the report more accurate we have updated how we supply this data in the report so it shows which user/agent actually authored the message sent. NOTE: This is also a prerequisite for us being able to display any kind of authorship in the front end within a conversation.
Reporting Inconsistencies Between Reports - Since our reports were built by different people at different times, there were some inconsistencies in column naming conventions, line selection dropdowns and other things that we cleaned up.
Bugs Resolved
HIGH - Messages Displaying Out of Order - There were some instances where in the initial display of a message history was out of order on a conversation that was recently updated. A refresh would set the correct order, but we fixed the issues with the initial view to eliminate confusion.
Page updated
Google Sites
Report abuse