Changelog
New updates and improvements
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
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
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
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
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