> 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-novembre-2024.md).

# Mises à jour Yoplanning – novembre 2024

November brought a lot of new features and improvements to **Yoplanning**! The focus was on performance optimization, improved credit tracking, and integration with **Google Things To Do**. Here's an overview of the main updates.

***

### 🎉 **New Features and Improvements**

🔹 **Real-time schedule update** 🗓: Changes made to the schedule (moving sessions, adding participants, changing monitors, etc.) are now visible **live** to all other team administrators. No need to reload the page to see the changes! This improvement is particularly useful for teams with multiple secretaries or a large number of monitors.

🔹 **Optimization of the credit and voucher system (BC)** 💳 :

* It is no longer possible to modify a product linked to a credit (whether the purchase or the use of a credit).
* When a credit was used and then cancelled, it was not always re-credited: this issue is now fixed.
* Deletion of vouchers already used (even partially) is prohibited.
* Unable to use credit for a 0€ order, to avoid incorrect transactions.
* The minimum amount usable in credit is now set at **0.01€**.

🔹 **Improved booking management**:

* When adding a product to the cart, a check prevents the number of places available from being exceeded.
* In the Booking Modules, the "Pay on site" option is now clearly displayed when the deposit is at 0%.

🔹 **Connection to Google Things To Do** 🌍 :

* A **Google Business Profile ID** field has been added in Team Settings, enabling integration with **Google Things To Do** to improve visibility of online activities.

🔹 **Advanced customization of products and sessions** 🎨 :

* Possibility to **define a custom color** for each product or session, facilitating the visual organization of the schedule.
* Added a **"short description"** field for products, which is used primarily in product list displays on the booking module.

***

### 🔧 **Fixes and optimizations**

✅ **Performance Improvement** 🚀 :

* Speeding up schedule loading (especially in a multi-team context).
* Improved loading performance of the Booking Module.
* Optimization of export and session management.

✅ **Corrections on orders and planning**:

* Orders placed by resellers at the counter now display correctly in "counter" mode and not in "online".
* Fixed an issue with **date of birth** displaying when editing a customer.

✅ **Removal of old obsolete integrations**:

* Removal of old **PostFinance** integration.
* Cleaned up test logs and old schedule sync methods.

***

💡 **These improvements are being implemented to optimize your experience on Yoplanning and offer you even more flexibility in managing your reservations.** If you have any questions or feedback, 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-novembre-2024.md?ask=<question>&goal=<endgoal>
```

`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.