The following enhancements are part of the December release for TSANet Connect 2.0. Go to connect.tsanet.org to find your Company and bookmark the new landing page.
New Updates: WebApp
- Added new Logo API (logo.dev)
- Fixed issues found with accessibility testing using https://wave.webaim.org (Contrast, labels)
- Modifications to the case detail page based on user feedback: All action buttons on top, Expandable fields for description and response note
- Enhancements to Partner sign-up process for Alliance Partner Programs: Company Website required, Enforce sign-up to include support manager, Auto-set the company note to include the business manager
- Fixed issue with the add note button not working on some emails
- Updated SSO Certs (SAML 2.0)
- Fixed issue with first use “update profile” pop-up after first use with SSO just in time user provisioning
- Allow multiple responses for information requests – to align with API functionality.
- Implemented auto-close for cases not active for 30 days
- Fixed issue where notes were not removed after 30 days
- Changes to the cases section of the homepage based on member feedback: Modified fields to show type and priority, Added a filter (Inbound Action Needed)
- Allow case close from the WebApp
- Updated Security headers to improve security
New Updates: Salesforce Package (1.0.19)
- Moved from unlocked to managed package
- Added actions and flows to allow for custom UI
- Fixed issue with outbound notes not adding to case feed
- Fixed issue with case approval from Salesforce
- Implemented information requested and rejection response types
- Fixed an issue where a new note was not displaying the user who created
- Updated case feed to include case update messages such as SLA missed, engineer change etc.
- Fixed issue with missing escalation instructions
- Implemented a method to refresh all cases
- Fixed issue with closing LWC new case action
- Improved test coverage to allow for deployment to production
- Added Internal Notes functionality (Add a note to other Members process forms)
- Added support for TAGs to be used within search (TAGs are added to process forms)
- Moved from Beta to General Availability
- Fixed issue with closure of LCW when triggered by action
- Moved to custom object to support TSANet Credential password masking and other features
GitHub link: Shows latest version, Install guide, and access to view source code
https://github.com/tsanetgit/SFDC
New Updates: Microsoft Power App
- A new Microsoft Power App was created for Microsoft Dynamics integrations, as well as an MS Teams App.
- Beta is now available for member feedback. Contact membership@tsanet.org if you would like to be included in this Beta.
GitHub link: Shows latest version, Install guide, and access to view source code
https://github.com/tsanetgit/MS_Power_App
New Updates: API
This release includes several 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
Updates and fixes:
- Custom endpoint for Cisco (Push – Push integration)
- Improved create notes endpoint to support Cisco integration
- Add Integration functionality and refactor integrations as post-processors
- Add GetCaseUpdatesSince, GetCasesCreatedAfter and GetNotesCreatedAfter
- Performance improvements, entity simplifications, and refactoring
- Fixed issue where inactive relationships were being returned
- Add health endpoints
- Update case priority message
- Add case creator name field
- Search now includes process form TAGs
- Internal Notes support for Process Form
- Add endpoints for case rejection, information requests, and responses
- Add better error handling and fix lazy initialization error
- Update note query to also accept caseIdOrToken and OpenAPI config
- Add the ability to provide information about the note submitter
- Align expectations for case response behavior and update case number when approval is updated
- Add threshold to Levenshtein distance calculation to avoid false positive matches
- Improve logging, add the ability to close case
- Allow for multiple info requests & responses
- Update endpoints for creating collaboration requests. Align language with that of the domain experts.
- Disable integration scanning and only add integrations when case or note is created from this instance
- Implement locking to prevent duplicate integration attempts
- Add new post note endpoint that returns just the created note.
- Fixed issue where tier selections were throwing an exception and updated documentation
- Fixed directionality of note integrations and adapt integration handling to account for that
- Fix integration ordering issue and case closure email bug
- Fixed case closure email bug