> For the complete documentation index, see [llms.txt](https://docs.xyb.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xyb.co/platform-release-notes/release-updates-and-announcements.md). # XYB Platform 1.1 Release Notes Release Date: 4/7/2025. Find out the top product/platform updates, performance improvements, and bug fixes from this release. ## V 1.1 Release Highlights {% embed url="" fullWidth="true" %} ## 1. Product Configuration ### Highlights * **Improved Product Configuration Usability:** Addition of a **templates component** enables reusable config structures and **custom timezone support** ensures time-accurate setups for global markets. * **Streamlined Import/Export FlowsL** Introduction of a new **Import** function and improvements to the **export** function make importing and exporting configurations smoother, clearer, and more actionable. * **Enhanced UI Consistency & Error Handling:** Major polish across dialogs, modals, and layout, including **standardized error handling**, **refined country value input**, **product version navigation**, and more intuitive controls like **disabled draft buttons** and **close actions**.
Supporting Improvements and Fixes * **Auditing & Schema Tracking:** More **granular audit logging** of sort/filter actions; schema versioning improvements; removal of unnecessary enforcement logic on product versions. * **Dialog & Interaction Enhancements:** Fixes and improvements for dialog triggers, range date pickers, version navigation, and product ref copy logic. * **Theme & CSS Fixes:** Resolution of theme override conflicts, post-CSS prefix issues, and **CSS isolation bugs.** * **Visual/UI Bug Fixes:** Corrections to icons, infinite loop behavior, export dialog rendering, toast re-renders, and ProductCard integration. * **Permission Evaluation:** Logic updated to use **token credentials** for evaluating permissions rather than identity directly. * **Versioning Documentation:** Documentation added to clarify **versioning logic** and integration standards for downstream teams.
## 2. Ledger ### Highlights * **Improved Status Management in Account Creation:** Users and systems can now **set account status during account creation**, providing more control during onboarding and reducing the need for subsequent patch operations. * **Better Context in Ledger Responses:** The **source of the transaction** is explicitly returned in the response as a `target` field, making it part of the formal record adding more transparency and traceability to ledger transactions and status transitions. * **Multilingual Support for Wallet Management: Estonian translations** and other localization enhancements have been added for wallet management and UI display.
Supporting Improvements and Fixes * **Service Schema Publishing:** Ledger service now publishes its **service configuration schema**, initial setup requests, and supports consuming configuration via topics with application-specific metadata (e.g., `appName`). * **Global Configuration Enhancements:** A `source` column was added to the `global_configuration` table for improved auditing and configuration lineage. * **OpenAPI Documentation Fix:** Missing OpenAPI definitions were corrected to ensure all service endpoints are well-documented for integrators and developers. * **Ledger Telemetry & Spring Boot Updates:** Telemetry and Spring Boot libraries were upgraded for better performance monitoring and platform compatibility. * **Permission Handling:** Ledger now uses **role-based permission evaluation**, aligning with other services in the platform. * **Several Database & Indexing Improvements**
## 3. Payments ### Highlights * **Dynamic Payment Field Enhancements & Currency Handling:** New support for **GBP and EUR payment routes**, **dynamic payment field migration** from legacy services, and **currency filters and sorting** in pay-history allow for a more intuitive, tailored, and localized user experience across international payment flows. * **Improved Payment History Interface:** Users can now benefit from **page restoration**, **shortcuts**, enhanced **filtering**, **associated payment visibility**, and table layout improvements.
Supporting Improvements and Fixes * **Kafka & Topic Enhancements:** Schema-related topics, Kafka consumer group naming, and partitioning logic were refined for more reliable messaging and improved integration with the rest of the data pipeline. * **Rate Initialization & Exchange Rate Improvements:** Bulk endpoints for initializing rates, validations for currency codes, new FX pairs (e.g., USD/GBP), and logic for incremental updates instead of destructive overwrites make currency rate handling more resilient. * **Auditability and Telemetry:** Role-based permission evaluation, logging libraries, telemetry integration, and metrics support have been expanded, enabling stronger observability for all services. * **Several Bug Fixes and improvements**
## 4. Accounts ### Highlights * **Wallet Linking and External References:** The account system now supports **direct links to wallets**, streamlining financial product connectivity. An **External Reference column** has been added to each account, allowing client systems or partners to associate their own reference IDs, which improves integration flexibility and visibility. * **Improved Page State and UI Experience:** A new **page state restoration** feature helps users return to previously selected views, filters, or scroll positions when navigating back and forth.
Supporting Improvements and Fixes **Auditing & Traceability:** Added **JPA listeners** and an `updatedBy` field to element entities to track who made changes. Controllers now include improved **information auditing** for better trace logs. **Account Metadata Improvements:** Added support for referencing the **account owner**, allowing stronger linkages between accounts and customer identity profiles. **Visual and UI Theming Fixes:** Adjustments were made to **theme overrides**, ensuring consistent styling across platforms and improved alignment with design systems.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.xyb.co/platform-release-notes/release-updates-and-announcements.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.