Jul 24, 2026, 12:43 AM UTC

Local time: Jul 24, 2026, 12:43 AM UTC

  • Updated: Vendor documentation links now indicate whether each link came from the vendor or from a specific integration, using catalogId / target on AiDocumentationLinkPreview. The existing saaSVendor.aiDocumentationLinks remains the aggregate list.
  • New: Personal Feed and Team Feed pages were added to the local command-center dashboard.
  • New: The createCustomFunction, updateCustomFunction, and updateStandaloneCustomFunction mutations now accept a pre-signed signedCodeJwt / signedCodeContextJwt pair (produced by the new Sombra customer-ingress sign route) as an alternative to a dhEncrypted payload for both GENERAL and DSR custom functions. This completes the CLI/CI flow for managing custom function code without an Admin Dashboard login.
  • New: New Sombra customer-ingress routes POST /v1/custom/sign and POST /v1/custom/unwrap, protected by the Sombra internal key bearer token, let the Transcend CLI and CI sign and retrieve custom function code without an Admin Dashboard login.
  • New: Org-level toggle on AI Settings to enable MCP × Sombra connectivity (default off). The UI is gated behind LaunchDarkly until ready. Turning AI off also clears the MCP × Sombra flag.
  • Updated: The DSR workflow New Wizard now requires at least one integration before continuing past the Integrations step, and before saving internal workflows or saving and publishing to the Privacy Center. Disabled actions show a tooltip explaining that requests need an integration or a skip integration if no action should run.
  • Fixed: Okta erasure DSRs no longer permanently delete users that were only being deactivated (for example, ACTIVE accounts).
  • Fixed: The delete button for file-upload fields on workflow config details now opens the confirm dialog and removes the field.
  • Updated: Preflight errors now appear in an Error Count column with a clickable count tag that links to affected requests, and include a retry button instead of floating row-action buttons.
  • New: Bulk retry for errors is available for a specific preflight from the Preflights page, without requiring a GraphQL script.
  • Updated: You can now create a new consent site and assign it to a theme directly from the Theme Editor.
  • Fixed: Consent record metadata key length validation now correctly allows keys up to 64 characters; a leftover hard-coded 20-character check that rejected longer keys was removed.
  • Updated: Consent record metadata now allows up to 50 keys (previously 10). Metadata keys may be up to 64 characters (previously 20). Metadata value length remains 64 characters.
  • Fixed: Logged-in users on the Sale of Info / Unverified Requests page now have their data subject derived from the authenticated session, instead of silently defaulting to the first configured subject. The data subject picker remains hidden for logged-in users and is shown only for logged-out visitors.
  • Updated: Admin GraphQL deployDraftVersionForPrivacyCenter now accepts an optional modules argument. Currently, only [MESSAGES] is supported.
  • Updated: The Admin Dashboard "Review Changes & Publish Privacy Center" modal now shows a secondary "Publish Messages Only" button whenever the Messages module has draft changes. This publishes only the messages module (a partial deploy) while leaving the rest of the draft unpublished. The button is available from every page that opens the review modal (General settings, Messages, Policies, and others).
  • Updated: Privacy Center footer links editor received layout and copy improvements, plus an icon upload empty state.