> 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/mises-a-jour-yoplanning-fevrier-2025.md). # Mises Γ  jour Yoplanning - FΓ©vrier 2025 ## πŸš€ New features ### βœ… Websocket * Adding/removing unavailability is now updated in real time on all secretaries' workstations, as with sessions. * Only the team members affected by the unavailability are notified. * Special case: When a session is moved by drag and drop onto an unavailability and is then "split", it is the team of the session that is notified (and not the team of the unavailability). ### Resource update * Now, the price of session template options is updated when the price of a global resource is changed. * The update is only performed if both prices (global resource and option) are identical before modification. ## πŸ› οΈ Bug fixes ### πŸ”§ Allotment Management * Fixed several bugs affecting the operation of allotments. ### 🎯 Promotions * Promotions on **session tags** are now correctly applied to subgroups (`session_tags` being stored only on the `main_group` in the database). ### 🏷️ Virtual sessions * Final fix for the virtual session issue in commands: an "unassigned" session is now created, with an overbooking alert on Slack and an email notification to the team. * Fixed a bug preventing virtual sessions from having correctly filled-in options. ### πŸ“„ Export and crate * Fixed a crash that occurred during cash register journal export. ### πŸ’° Payments * Fixed a bug where the "check all" button was not displaying the correct data in the payment list (date not taken into account). * Fixed a bug where payments made **exactly at midnight** were attributed to the wrong day. ### πŸ›’ Orders * Several corrections to the **check-order** for better management of aggregations and virtual sessions (replaced by an overbooking system). * Fixed a bug in the fee list where multiple actions did not take into account lines excluded by "check all". ### πŸ“© Emails * Another attempt to send an email to the end customer after a sale in "pay on site" mode. ### πŸ” API * Correction of the filters `nb_tickets__gt, __gte, __lt, __lte` for the correct consideration of allotments. * Critical correction: sessions with `max_participant=NULL` (infinite) were incorrectly blocked in online sales. ## ✨ Improvements ### 🎨 Interface and user experience * The **Save** button in the command editor is now disabled and then re-enabled to prevent multiple clicks. * The reseller lists are now sorted alphabetically. * When deleting a bonus (reward), if it is still linked to a session, an error is displayed with a red alert. * Cancellation of the **email deposit 0** fix, deemed too risky for reservation management. ### πŸ“‚ Export * It is now mandatory to enter both date filters (start and end) to export XLS or PDF files. This prevents errors that could overload the server. *** ### 🎯 Conclusion This February 2025 update brings significant improvements to real-time outage management, option price synchronization, and advanced payment processing. Numerous bug fixes have also been implemented to ensure a smoother and more efficient user experience. πŸ’ͺ Thank you for your trust, and see you soon for more improvements! πŸš€πŸ”₯ --- # 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/mises-a-jour-yoplanning-fevrier-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.