Skip to main content
March 2025 Release Notes
The platform gained a callback system and component tester framework this month, while Compliance Hub received major improvements to document handling, entity management, and field mapping.

Platform

  • Callback support: Flows can now register callbacks that execute when specific conditions are met, enabling asynchronous patterns like waiting for external webhook confirmations before proceeding
  • Component tester framework: New testing framework for building and running integration tests against individual components, making it easier to validate component behavior in isolation
  • HTTP JSON response matching: The HTTP connector can now match and route based on JSON response content, enabling conditional branching based on API response payloads
  • Attribute find fix: Resolved ambiguity in the attribute find method that could return unexpected results when multiple attributes shared similar names
  • Component closure caching: Optimized how component closures are cached in memory, reducing processing overhead for frequently invoked components
  • Null attribute removal: New removeNulls() method on attributes strips null values before forwarding data, simplifying downstream processing logic
  • Component revision optimization: Optimized the component revision resolver to reduce resolution time for deployments with many component versions

Studio

  • Analytics provider save/load fix: Fixed an issue where analytics provider configurations were not correctly saved or retrieved from target settings
  • Loader component fix: Resolved a rendering issue with the loader component in the template that could cause flickering during page transitions
  • Translation corrections: Fixed mistranslated UI strings that affected the localized experience in several languages
  • Onboarding redesign: Rebuilt the onboarding flow with a refreshed visual design and updated content
  • Target preview accuracy: Preview rendering now uses the resolved configuration, ensuring what you see in the Studio matches the deployed experience
  • Test assertion messages: End-to-end test failures now include human-readable assertion messages, making test debugging significantly faster
  • Library credential module: New module for obtaining component credentials through library backend functions, enabling secure credential exchange for third-party integrations
  • Target name via settings: Target names can now be changed through the settings data API instead of requiring a separate update call

Client SDK

  • Deprecation warning fixes: Resolved React deprecation warnings that appeared in the browser console during verification flows
  • Store2 security update: Updated the store2 dependency to address a security vulnerability in local storage handling

Compliance Hub

  • Document name display: Verification document components now display the actual document name in the header instead of the generic “Other” label
  • Auto-create Account for Contacts: When a Contact is created or updated without a related Account, the system now automatically creates one, preventing orphaned contact records
  • Source of Wealth/Funds mapping: Added field mapping and UI display for “Source of Wealth” and “Source of Funds” data, surfacing important compliance information from the “Other” document type
  • Multiple “Other” document support: The verification component now correctly processes and displays multiple documents of the “Other” type within a single verification
  • Lookup field email/mobile mapping: Fixed an issue where email and mobile fields from lookup object mappings could not be used in verification request workflows
  • Verification data retry parameter: Added a configurable “Maximum Verification Data Retries” parameter that is passed to the tokenizer request, controlling how many times the system retries data retrieval
  • Verification prerequisite check: The system now validates that verification documents are properly defined before allowing a new verification to be created
  • Field mapping type conversion fix: Resolved an “Invalid conversion from runtime type Id to Map” error that occurred in specific field mapping configurations