Skip to content

TSANet Connect 2.14 ( Release )

Latest

Choose a tag to compare

@orestvasylenko orestvasylenko released this 21 Oct 15:33
· 4 commits to main since this release

TSANet Connect 2.14.0.

Install:
Production: https://login.salesforce.com/packaging/installPackage.apexp?p0=04tgL000000aQjxQAE
Sandbox: https://test.salesforce.com/packaging/installPackage.apexp?p0=04tgL000000aQjxQAE

Documentation: https://tsanet.gitbook.io/connect/documentation/salesforce-app/installation-guide

Highlights

  • Webhooks via Platform Events. Inbound webhooks are received by a REST endpoint and published as TSANetWebhookEvent__e platform events; the event trigger upserts TSANet Cases, Notes and Responses and fires subscriber flows. No manual refresh is needed to see partner updates.
  • Webhooks require an External Client App. The webhook endpoint is exposed only through an External Client App (OAuth 2.0 client credentials). Connected Apps and legacy unauthenticated callbacks are no longer supported.
  • Authentication via Named Credentials only. TSANet API calls are authenticated exclusively through Named / External Credentials (OAuth 2.0). Basic Authentication (username / password stored in the package) is no longer supported - existing orgs must migrate before upgrading.
  • Security hardening for AppExchange review. All SOQL/DML runs in USER_MODE with explicit CRUD/FLS checks; FeedItem inserts use Database.insert(..., AccessLevel.USER_MODE). Code Analyzer v5: 0 Critical/High. Graph Engine: 0 FLS violations. 2.14 PASSED Salesforce Security review on Oct 30th.
  • OEM use case features. Note Type added to enable end-end workflows. Document ID added to identify inbound process used

Important

Breaking change: Basic Auth credentials and Connected App-based webhooks stop working after upgrade. Configure a Named Credential and an External Client App first - see the setup guide.

Issues Fixed

#201 Outbound TSANet auth uses the OAuth2 Client Credentials flow through Named Credentials. Username and password are no longer stored on the credential record.
#191 Inbound webhooks use a Salesforce External Client App. The callback runs as the Integration User on the org domain.
#219 Creating a TSANet Credential now sets the Named Credential and Integration User and marks one record as primary.
#244 Test environment added (connect2.tsanet.us). Dev, Beta, and Prod names are aligned with their Named Credentials.
API
#172 Notes use the v2 notes contract (CaseNoteTemplateDTO, including note type).
#245 Collaboration list, paged reads, and webhook registration use /v2. Approve, reject, close, and information actions stay on /v1.

Notes and Case Feed

#215 Several automated outbound notes are sent as separate notes, not merged into one.
#163 The connector shows Document Id and file name.
#241 A note added on a Salesforce Case is sent to TSANet and linked to the collaboration request.
#181 Strikethrough is kept in note text.
#197 Indentation is kept in note text.
#198 Center and right alignment are kept in note text.
#233 Case Feed Member shows the partner company, not the wrong value.
#231 The submitter of a request created in Salesforce is the Salesforce user, not the integration user.

Security Improvements

  • The Aura method no longer returns the org-wide API base URL.
  • Old secret fields removed. Secrets stay in Named Credentials and External Credentials.
  • The test class is no longer in the shipped guest permission set.
  • CRUD and FLS checks added on the reported paths.
  • SOQL uses bind variables.
  • Debug logs removed from error-handling paths.
  • Case queries always have a filter.
  • Non-selective query limited and filtered.
  • Empty trigger removed.
  • Aura callouts are no longer a chain of synchronous callouts.
  • Client-side caching added where data is reused.
  • Attachment upload no longer risks heap exhaustion.
  • Remaining large-data and bulk issues fixed.

Flow Improvements

  • Auto Accept flow stays a deactivated template.
  • Improved the Auto-Accept flow to runs asynchronously (runAsync), so activating the flow no longer fails on a callout in the same transaction. If member have activated and modified the old flow replace it with this new one.
  • Accept, Reject, and Request Information screen flows return an error to the screen instead of an unhandled fault.
  • The notification subflow skips an inactive Case owner.
  • Inbound trigger flows (Collaboration Request, Asset, Auto Accept, Note Trigger, Request More Information) ship as deactivated templates. Subscribers clone and activate them.
  • Screen flows and the notification, owner-change, and case-link flows are Active.