> 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/2021/v1.4.0-6th-april-2021.md).

# V1.4.0 - 6th April 2021

Our first major release of 2021 - We have carried out a number of upgrades to our platform to make UMA Vision a leading space management tool.\
We have built-in new "Map Features" for our Mobile UI and for users to Book meeting rooms or desks from the floor map feature using their own user login. 

Our new all one Environmental sensor has been added that will show you the following information

* Humidity
* Temperature
* Co2 Intensity

 

These sensors are used in conjunction with our cisco API so data can be consistent across meeting rooms.

We have also improved the user interface for managing multiple buildings and floors within your organisation on our analytics dashboard. 

Our Cisco Webex device integration has also had additional details added to the UI Allowing you to see a number of statistics from the room, including.

* Room Temperature 
* Room Humidity 
* Room Occupancy 
* Ambient noise 
* Sound level\ <br>

As well as this we have also rectified a number of minor UI Bugs and fixes within the backend of the platform.

Microsoft Teams bot has had major improvements on the conversational flow and the UX to find the right space you need.&#x20;

Cisco Webex Bot has had the same improvements as our Microsoft bot for a better User Experience.

<table data-header-hidden data-full-width="false"><thead><tr><th></th><th></th><th width="100"></th></tr></thead><tbody><tr><td><strong>Feature</strong></td><td><strong>Version</strong></td><td><strong>Release Date</strong></td></tr><tr><td>Floor Map view for Mobile</td><td>V1.4.0</td><td>07/04/2021</td></tr><tr><td>Add UMA Co2, Temp and Humidity Sensor</td><td>V1.4.0</td><td>07/04/2021</td></tr><tr><td>Create 'Floor' Entity and Assign Floor Map</td><td>V1.4.0</td><td>07/04/2021</td></tr><tr><td>Create 'Floor Map' Entity</td><td>V1.4.0</td><td>07/04/2021</td></tr><tr><td>Floor Entity Support for Bot and Mobile</td><td>V1.4.0</td><td>07/04/2021</td></tr><tr><td>Floor Map View for Admin</td><td>V1.4.0</td><td>07/04/2021</td></tr><tr><td>Update to Navigation Menu</td><td>V1.4.0</td><td>07/04/2021</td></tr><tr><td>Floor Map View for User</td><td>V1.4.0</td><td>07/04/2021</td></tr><tr><td>Book a Desk &#x26; Room from Floor Map </td><td>V1.4.0</td><td>07/04/2021</td></tr></tbody></table>

![](blob:https://askuma.atlassian.net/5b28baad-5bdd-404c-b1d0-c687cf9145a1#media-blob-url=true\&id=b53d5b50-5770-4bf1-bcf3-c9057de9f290\&collection=contentId-989233241\&contextId=989233241\&height=72\&width=697\&alt=)

&#x20;


---

# 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/2021/v1.4.0-6th-april-2021.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.