> 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-2024/mises-a-jour-yoplanning-decembre-2024.md). # Mises Γ  jour Yoplanning – dΓ©cembre 2024 In December, **Yoplanning** introduced new features to improve booking management, strengthen integration with **Ginkoia** and optimize overall performance. Here are the main updates of the month! *** ### πŸŽ‰ **New Features and Improvements** πŸ”Ή **Integration with Ginkoia** 🎿 : Some of our customers use **Ginkoia**, a ski rental fleet management solution. To make their work easier, we have implemented an **automatic order synchronization system** containing rental equipment. * When Ginkoia material is added to an order (via a special tag), an **XML** file is automatically sent to Ginkoia. * XML sending is currently done by email. This is a somewhat "old school" version pending integration via API at the initiative of the Ginkoia company. πŸ”Ή **Reading QR Codes in the Android mobile application** πŸ“± : * A new feature allows you to scan **YoPlanning QR Codes** directly from the Android app. * A QR Code icon is available in the menu to facilitate access to this feature. * The iOS app is pending deployment. πŸ”Ή **Improved session repetition management** πŸ”„ : * A new **repetition list** is available to easily see which sessions are affected. * A filter now allows you to search for **repeated sessions** for better visibility. πŸ”Ή **Added a confirmation message when moving participants** 🎯 : * When a participant is moved to another session, a confirmation message is displayed to avoid any confusion. *** ### πŸ”§ **Fixes and optimizations** βœ… **Promo code management** πŸ’³: * Fixed a bug that allowed deleted promo codes to be used. * It is now impossible to create a **duplicate promo code**: an error message will be displayed if a code already exists. * Fixed a crash related to promo code status when adding a booking. βœ… **Optimization of the booking module (Booking Engine, BE)** πŸ›’ : * Fixed a bug on the integration of **hyperlinks** in reservations. * When selling credits or vouchers at the counter, an **empty label** was displayed on the invoice: this is now corrected. βœ… **Improvements on accounting and team management** πŸ“Š: * Improved error handling for **Team IDs in Pennylane**. * Internal invoice synchronization has been fixed to avoid input errors. * **The "unassigned line" field has been slightly enlarged** for better readability. βœ… **Graphic and email corrections** βœ‰οΈ: * On Gmail and other email clients, **bullet points were displayed incorrectly** in emails: this has been fixed. * Fixed a graphical bug on the **dashboard**. *** πŸ’‘ **These improvements are designed to make your use of Yoplanning even more fluid and efficient.** If you have any questions or suggestions, do not hesitate to contact our support. **Thank you for your trust and see you soon on Yoplanning!** πŸš€ πŸ”Ή **The Yoplanning team** --- # 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-2024/mises-a-jour-yoplanning-decembre-2024.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.