Changelog
New updates and improvements
Mar 2026
See what’s new and improved in our March update.
Main features
New second-generation Salesforce package (v2.9) with multiple new features
Added webhooks, providing API support for real-time updates and eliminating delays caused by polling intervals
Updated Microsoft Dynamics package to include webhook support
Multiple web application improvements
WebApp - https://connect.tsanet.org
Added a new feature allowing Member Admins to update passwords for API users. This feature is available on the Company Admin page.
Updated the Phone Number field by splitting it into two fields: Country Code and Phone Number and refreshed the country code library to reflect accurate country listings.
Modified the Member Feedback Survey template and changed to send 48 hours after case closure.
Updated email templates to reflect the new TSANet branding.
Updated footer links and refreshed the Partner Program Playbook link.
Fixed an issue with exporting reports and viewing companies in the TSANet Super Admin interface.
Updated email logic to exclude API users from receiving system emails.
Fixed an issue with the phone number field not saving correctly on the Collaboration Request response form.
Updated email‑sending logic to run within a try‑catch block to improve reliability.
Modified a custom field to resolve a configuration issue.
Fixed an issue related to Mandrill email delivery.
Resolved an issue affecting Partner Program page banners.
Updated the username field to be case‑insensitive.
Added security to support Soverign Support use case
Salesforce Connector - https://tsanet.gitbook.io/connect/documentation/salesforce-connector/installation-guide
This is a major new release that provides many new features and improvements. The package was also moved to the second-generation package model that will provide long term support for updates.
Enhanced environment configuration and integration user handling, including improvements to Azure environment definitions and integration user email updates.
Improved connector reliability by reviewing and enhancing polling behavior, laying the groundwork for more efficient long‑polling and event‑driven updates.
Added a new Escalation action to the Salesforce Case process, providing faster and more consistent escalation handling.
Enabled automatic linking of inbound TSANet collaboration requests to existing Salesforce Cases when applicable.
Improved the Lightning Web Component (LWC v2) experience by resolving layout issues, duplicated widgets, and unexpected empty frames during collaboration request creation.
Corrected issues with product and company selection lists, ensuring values now display and load correctly in collaboration request forms.
Resolved multiple attribution issues where cases, notes, or feed entries were incorrectly shown as created by the API user instead of the actual submitter.
Fixed issues allowing notes to be created with null or incomplete information and ensured notes now reliably reflect accurate creator and content details.
Standardized naming conventions so all TSANet‑provided Salesforce Flows now begin with “TSANet,” improving admin visibility and maintainability.
Updated scheduled job management so the TSANet Scheduled Job “Manage” button correctly opens the configuration window.
Resolved issues where customer, company, or creator information displayed as null or N/A in collaboration feeds and case views.
Improved collaboration feed behavior to ensure escalation instructions and case updates appear correctly for both senders and receivers.
Microsoft Dynamics Connector - https://tsanet.gitbook.io/connect/documentation/dynamics-connector/demo
Implementation of collaboration request webhooks.
New configuration UX, where you can easily set up connection and register webhooks.
New seamless UX that keeps user updated.
Fixed issue where duplicate notes were created
Fixed issue with refresh when user changed tabs
Improved error handling on form submission
resolved an issue where special characters in a note could create error
API - https://tsanet.gitbook.io/connect/api-reference
Add webhook support
Refactor integration processing to use integration IDs
Improve authentication error handling with structured error responses
Centralize public endpoint security path patterns
Disable vector sync scheduler by default
AI module cleanup
Feb 2026
See what’s new and improved in our February update.
Connect 3.0 Architecture Changes
Architecture changes to support features for Connect 3.0 and improve performance and reliability of the platform.
Migrated all environments to Azure Hosting
Upgraded all technology for the WebApp
Migrated to PostgreSQL database
Migrated to ActiveMQ Artemis message broker
Migrated to Better Stack for system monitoring and incident handling
WebApp - https://connect.tsanet.org
Added support for multiple email domains
Fixed an issue where emails were sent to API user
Fixed an issue with Company Profile that introduced additional null domain
Added API solution to allow Partner sign-up from a Members web: See Integrated Partner Registration | Documentation | TSANet Connect
Fixed issue with exporting certain reports
Salesforce Connector - https://github.com/tsanetgit/SFDC/releases/tag/Release-v1.17
No changes for the Salesforce connector. New Second generation connectorplanned for March Release.
Microsoft Dynamics Connector - https://appsource.microsoft.com/en-us/product/dynamics-365/tsanet-org.tsanetd365-preview?flightCodes=340d37952f0d4d9cbea160681bbb908c
Modified method to accept case and auto-link MS Dynamics Case
Added flows to automate inbound requests
API - https://tsanet.gitbook.io/connect/api-reference
Added email validation in transactions
Fixed issue with html characters in email field
Fixed issue with access to a process form within a private group
Fixed an issue with certain field types in a solution support process form
Oct 2025
See what’s new and improved in our October update.
Gitbook Documentation
GitBook is the new location for all documentation, including Developer, Support information, and Changelog
Inbound Process Automation (Connectors)
Inbound process automation to create cases and respond to inbound requests
Includes entitlement checks (For example, serial number of an asset in Salesforce)
WebApp - https://connect.tsanet.org
Company Email Domain - As part of our ongoing commitment to data security, all user accounts are required to use an approved company domain. Personal email domains such as gmail.com, yahoo.com, and outlook.com are no longer accepted. Authorized subdomains and additional company-owned domains are supported.
Removed Parent - Child and MS Teams process form types
Fixed an issue found when updating the Case owner as the Submitter
Modified the Limited Member's description on the TSANet Members page: https://www.tsanet.org/members/
Logo.dev on tsanet.org was exceeding usage limits. Made a change to only share 20 rows at a time and have the user page through the list or search.
Modified emails to be sent as text and html (MIME parts)
Improved the text for setting password on the WebApp
Fixed an issue with notes not displaying correctly
Fixed an issue found with the View/Test button on Process Form
Made modifications to the Company Profile
Disable emails for users of Role = API
Changed the Role name of "Caller" to "Standard User"
Changed the process form "Ticket Type Document" to "Collaborative"
Added the user Role as read only field on Member "Profile"
Allow Member Admins to create API Users
Updated the TSANet Connect Logo and "training" link
Salesforce Connector - https://github.com/tsanetgit/SFDC/releases/tag/Release-v1.17
Company Email Domain - As part of our ongoing commitment to data security, all user accounts are required to use an approved company domain. Personal email domains such as gmail.com, yahoo.com, and outlook.com are no longer accepted. Authorized subdomains and additional company-owned domains are supported.
Added a confirmation option when closing a TSANet Case.
Implemented system recovery enhancements to better handle and recover from unexpected errors.
Enabled the ability for both the sender and receiver to update case information.
Added file versioning support for TSANet Case attachments.
Included the integration user field on the TSANet Credentials page layout.
Fixed an issue where collaboration requests created from the WebApp were not properly creating or attaching TSANet Cases in the connector.
Resolved an issue where outbound notes were incorrectly displayed as entered by the integration user.
Fixed a bug where creating a case without contact information initially caused an error when later creating a new TSANet Case.
Addressed a duplication issue where outbound TSANet requests were generated with the same token, requiring manual cleanup.
Microsoft Dynamics Connector - https://appsource.microsoft.com/en-us/product/dynamics-365/tsanet-org.tsanetd365-preview?flightCodes=340d37952f0d4d9cbea160681bbb908c
Company Email Domain - As part of our ongoing commitment to data security, all user accounts are required to use an approved company domain. Personal email domains such as gmail.com, yahoo.com, and outlook.com are no longer accepted. Authorized subdomains and additional company-owned domains are supported.
Enhancement made to allow the Sender/Submitter to update the case (example: change of case owner or MS dynamics case)
Enhanced the notes in timeline by adding the Company name
Updated installation guide to include updates to the solution
Fixed an issue where outbound cases created duplicates
Made an improved to the customer section when creating a TSANet Case
Trigger auto-refresh when Note is added to TSANet Case and when a user Updates Approval ( example: change of case owner or MS dynamics case)
API - https://tsanet.gitbook.io/connect/api-reference
Support for sub-domains with email validation – user actions can now be validated with primary and alternate domains. Setting is in WebApp Admin
Improved security with new case and notes – Validate user email domain. System will return error if email domain does not match setting for the account
Fixed issue found in manual penetration testing – SQL injection
API now supports update case for both sender and receiver
Fixed issue with special characters in API password
Last updated