> ## Documentation Index > Fetch the complete documentation index at: https://docs.zenoo.com/llms.txt > Use this file to discover all available pages before exploring further. # July 2025 July 2025 Release Notes The platform introduced configurable memory buffer limits and an improved component testing framework, while Studio overhauled permissions storage and Compliance Hub added WorldCheck ongoing monitoring. ## Platform * **Configurable memory buffer limits**: Added a `max-in-memory` buffer size setting for WebFlux, preventing out-of-memory issues when processing large file uploads or API responses * **Component tester improvements**: The component tester now uses the Component Factory pattern, providing more realistic test execution and better parity with production behavior * **Component tester documentation**: Published the component tester documentation on the platform docs site, making it accessible to all integration partners * **Transport base URL support**: Fixed base URL configuration support in the HTTP transport layer, enabling components to use relative paths with a configured base URL ## Studio * **User permissions compression**: Overhauled how user permissions and library access are stored, compressing the `availableLibraries` field and migrating to a more efficient storage format for better scalability * **Target cache cleanup**: Each target now has its own cache folder that is cleaned up independently, preventing stale data from one project from affecting another * **Encrypted test environments**: Cypress test environment variables are now encrypted, preventing accidental exposure of API keys and credentials in CI/CD logs * **File support for API-only targets**: API-only verification targets can now accept and process file uploads, expanding headless verification capabilities to document-based flows * **Validator result clearing**: Added a button to clear validator results from the top bar, making it easier to reset validation state during flow development * **Code suggestion fix**: Resolved a bug in the code suggestion feature that could recommend incorrect completions in certain contexts ## Client SDK * **Accessibility features**: Added accessibility improvements including proper ARIA attributes, keyboard navigation support, and screen reader compatibility for verification flow components * **Google Maps API key handling**: Fixed handling of falsy API key values in the Google Maps integration, preventing initialization errors when the key is not yet loaded * **Mixpanel error capture**: Console errors are now captured and forwarded to Mixpanel for centralized error monitoring across deployed verification flows ## Compliance Hub * **WorldCheck ongoing monitoring**: Added a daily scheduled job that checks for updates in WorldCheck screening results, with case system ID tracking for continuous monitoring of screened entities * **Case rating endpoint**: New endpoint and modal for managing case ratings, enabling supervisors to rate and review the quality of completed case assessments * **Risk and reason in case results**: The case result summary box now displays both the risk level and the reason for the decision, giving reviewers immediate context * **Report data enrichment**: Reports now include all content from the Other\_Data field, ensuring no verification information is lost in PDF exports * **Worldview split API calls**: When user interaction is not required, the system now makes separate API calls for address and identity verification through Worldview, improving data completeness * **Provider subtype corrections**: Fixed the "Qualid" provider subtype display to show the correct "Qual-ID" branding * **Document part consistency**: Document groups now always include individual parts even when only one document is present, ensuring consistent rendering in the review interface * **Country type normalization**: Standardized the country field format in API responses to use consistent type codes across all endpoints * **Date handling fix**: Resolved an "Invalid Date" error that could occur in upsert record responses when date fields contained edge-case formats * **Verification action keyboard fix**: Resolved an issue where pressing space or enter on a verification action button would clear the status instead of triggering the expected action