> For the complete documentation index, see [llms.txt](https://support.meetuma.ai/uma-knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.meetuma.ai/uma-knowledgebase/release-notes/web/2022/v2.9.8-27th-october-2022.md).

# v2.9.8 - 27th October 2022

This release is all about improving the way you can book and manage car parking spaces within UMA.

**🅿 Car Parking Improvements**

 

**Parking Space Attributes**

To start we've added some attributes to the car parking resource so you can choose to tag the space as a disabled ♿ or EV charging space 🔌

<figure><img src="https://627748108-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0shDrJltbdGiCRz6ip4Z%2Fuploads%2FHa7ZQBG1mkUyAa3tOnza%2Fparkingresource.gif?alt=media&amp;token=64136249-8547-4fce-8553-1da3425caf9a" alt=""><figcaption></figcaption></figure>

**Car Parking View**

We've added a new car parking view to the **'Workspace'** page.

This allows you to quickly filter down to view available parking spaces to book on the day you're coming into the office.

You can also easily identify if a space is allocated as a disabled ♿ or EV charging space 🔌.

Administrators, advanced managers and manager roles can understand parking space utilisation and view detailed information about each parking booking.

&#x20;

<figure><img src="https://627748108-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0shDrJltbdGiCRz6ip4Z%2Fuploads%2FzkIoKaedrosXSd2B1b7b%2Fparkingview.gif?alt=media&amp;token=50bcc2c3-59a4-44aa-aed2-39dc89fdf749" alt=""><figcaption></figcaption></figure>

**New Booking Fields**

We've added the following fields to the parking booking form:

* Car Registration
* Make
* Model

These fields are mandatory and allow administrators, advanced managers and manager roles to quickly view who is parked in a space by hovering over the booking.

These user roles are also able to book on behalf of and edit or cancel another users parking space booking.

&#x20;

<figure><img src="https://627748108-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0shDrJltbdGiCRz6ip4Z%2Fuploads%2FEXqkXqtGqRFQJjmeX3jO%2Fbookingfields.gif?alt=media&amp;token=b5a428e7-d234-4e2c-9897-da82a7539ce7" alt=""><figcaption></figcaption></figure>

**Parking View on Map**

We now have basic support to allow parking spaces to be assigned to a map.

Get in touch with the team for more information on this.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.meetuma.ai/uma-knowledgebase/release-notes/web/2022/v2.9.8-27th-october-2022.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.