TSANet Connect – February 2025 Release

The following enhancements are part of the February 2025 release for TSANet Connect 2.0.

New Updates: WebApp

  1. When the response SLA is missed, a note is added that includes the escalation instructions.
  2. Initial Response details added as a note
  3. Fixed remaining accessibility issues identified by https://webaim.org/
  4. Improved case detail view – Now shows status
  5. Fixed issue with outbound bcc functionality
  6. Fixed issues with TSANet Admin reporting
  7. Enhanced user profile to show regional focus group
  8. Fixed issue where Member admins were not able to export reports

New Updates: Salesforce Connector

GitHub link: Install the latest version, view installation and user guides, report issues, and access the source code https://github.com/tsanetgit/SFDC

  1. The general availability version of the package (V1.2) now allows for upgrades.
  2. When the response SLA is missed, a note will be included with the escalation instructions.
  3. Initial Response details added as a note now shows in case feed
  4. Fixed issue where notes were out of order in the case feed
  5. Action buttons reflect the status of the case (Example closed case does not allow actions)
  6. Added flow to allow for notification to user for inbound notes
  7. Fixed issue with View-All from Lighting web component
  8. Fixed issue where all open TSANet cases could show on the LWC
  9. Fixed issue where “T” was added to the notes feed
  10. Fixed issue where the scheduled job would not trigger notification flow
  11. Fixed issue where user/pass in the TSANet credentials could return an error
  12. Fixed issue with error displayed during new case
  13. Fixed flow error – Improved flow to validate valid-user
  14. Improvements in workflow for Information requested case status
  15. Improvements to Case notes and integration to Salesforce case feed
  16. Fixed issue where fields could be out of order in different locations

New Updates:  Microsoft Dynamics Connector

GitHub link: Install the latest version, view installation and user guides, report issues, and access the source code https://github.com/tsanetgit/MS_Power_App

  1. Moved to Beta – Contact TSANet if you use Microsoft Dynamics. Please get in touch with membership@tsnet.org for access.
  2. Fixed issue where update response gave an error.
  3. Added a new list view (Action Needed)
  4. Improved search performance (Find member)
  5. Fixed issue with Approve, Information Requested, or Reject inbound request
  6. Fixed some field naming issues – To align with WebApp and Salesforce connector
  7. Fixed issue with Priority setting
  8. Created rules to prevent new notes on closed or rejected cases
  9. Improved Response section
  10. Improved navigation
  11. Improved list detail to show the member you are working with
  12. Overall UI Improvements
  13. When the response SLA is missed, a note will be included with the escalation instructions.
  14. Initial Response details added as a note
  15. Fixed issue with Tier Select

New Updates:   API

This release includes new and updated endpoints that improve functionality and integration options.  More information on the TSANet Connect API, including Swagger docs and Postman collection, can be found at the link below:

https://www.tsanet.org/api-integrations

  1. Return case number from latest approval
  2. Enhance logging and fix the approval note.
  3. Unify language, lay grounds for better error responses, sunset salesforce + field specific metadata endpoints.
  4. Default note priority to low if not provided
  5. Improve outbound note integration – Push integrations to jms queue
  6. Update integrations before enqueueing and bump version
  7. Add display order to field statuses and clean up tests
  8. Improved integration performance
  9. Limit query to 10 integrations
  10. Remove case entry entity graph in favor of lazy loading
  11. Improvements with queueing
  12. Fix flaky test
  13. Update integration timestamp when setting status
  14. Exclude removed notes by default.
  15. Apply ordering to the case status endpoint.
  16. Improvements to case identifiers and usage for response
  17. Enhance GET Cases to allow the return of a single
  18. Resolved the issue where the WebApp and Connectors did not display the same data for approved cases.