> For the complete documentation index, see [llms.txt](https://docs.yoplanning.support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yoplanning.support/en/information-de-mise-a-jour/rapport-de-maj-2025/mise-a-jour-yoplanning-mai-2025.md). # Mise ร  jour Yoplanning - Mai 2025 Here are the latest updates to Yoplanning for May 2025. Technical improvements, new features and important fixes are included to further optimize your experience! *** ### โœ… New products #### ๐ŸŒ Multilingual * In all **multilingual fields**, the first tab displayed now corresponds to the **user interface language**. A significant improvement in usability for multilingual users! #### ๐Ÿ“ Advanced Filters * In the **planned resources** view, a **filter by staff** has been added to facilitate the search for resources assigned to a specific supervisor. #### โ„น๏ธ Information bubbles (Planning) * A tooltip appears when hovering over sessions and unavailability in the schedule. This setting is enabled by default but can be disabled in your preferences. #### ๐Ÿค– AI & Translation * Artificial intelligence now pays more attention to **proper nouns** (especially team names) and no longer translates them. *** ### ๐Ÿ› ๏ธ Fixes #### ๐Ÿงพ Orders & Sessions * Correction to the `origin` filter: **accents** are now correctly taken into account. * When deleting a participant, it is now the **parameter "close sale after the 1st order"** (and not "price per session") that is used to decide whether or not to delete the associated session. #### ๐Ÿ“… Planning & Rehearsals * An unintentional overlap could be created if you defined a **multi-session over 2 days** with a weekly repetition: this case is now detected and blocked. * **Improved performance** for large accounts on the schedule (especially drag'n'drop). * Fixed a critical bug that **prevented moving or modifying sessions** due to fee restrictions. #### ๐Ÿงฎ Calculations & Displays * Fixed display bugs on **XS inputs** and icon alignment. * The **PDF "resource summary"** only take into account **date filters**, this behavior remains unchanged. * Fixed bug regarding pricing for options with **percentage price** + price variation. * The PDF participants button in the session will no longer be **hidden** incorrectly. * The **restrictions on fee orders** have been strengthened for greater consistency. *** ### ๐Ÿ”„ Modifications * **Behavior of the "existing booking" field** changed: it is no longer limited to 2 months, but the search is now only possible among 5 displayed items. * The Yoplanning favicon is now **blue** for backoffice users (`BE`). * In **business introducer** mode, graphical improvement: fewer white squares and a link to the appropriate help center. *** For any questions or assistance with implementing these new features, please contact our support team at: See you very soon for the next developments! --- # 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.yoplanning.support/en/information-de-mise-a-jour/rapport-de-maj-2025/mise-a-jour-yoplanning-mai-2025.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.