> For the complete documentation index, see [llms.txt](https://docs.gmetri.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gmetri.com/features/release-notes/2021/11-17-nov-update.md).

# 11-17 Nov Update

November 2021 Update (Teaxr v0.5.1483)

### :rocket: Major Features

* Editor
  * Added safe names for files uploaded and variables names to resolve special characters.

### :arrow\_double\_up: Minor Improvements

* Editor
  * Updated preferences page in deployment section
  * Added functionality to download comments from the Publish section
  * Improved updates from number/decimal properties
  * Revamped variables and support sections.
  * Added relevant toasters and loading indicators.
* Viewer
  * For embed HTML element, popup mode becomes full screen on mobile phones
  * Error screen with refresh button added for experiences with stale login.

### :bug: Bug Fixes

* Viewer
  * Fixed inconsistent height for quiz element
  * Fixed multiple updates in singular option not happening in quiz element
* Portal
  * Fixed analytics page views table UI and functionality.
  * Fixed geolocate failures


---

# 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://docs.gmetri.com/features/release-notes/2021/11-17-nov-update.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.