> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/release-information/flow/6.13/6.13.11.md).

# 6.13.11

Released 2021-06-29

**Web client:**

* Added drop down list beside the paging where the user can set how many rows are to be shown. The setting is saved so the same amount of rows are shown the next time the user gets to the grid.
* Illegal xml characters will not stop export of database anymore.
* Changed behavior of grid to adjust the “FIT” columns to also take header text length into account.
* Fixed an issue which caused a column to become 0px width, which caused the grid to be higher than expected.
* Checkbox is not a fixed size in the web client which caused problems when the header was longer.

 **Flow studio and Flow server:**

* Illegal xml characters should not stop export of database anymore.
* Monitoring results are shown in Studio on initial load and after sorting columns.

**Workflow engine:**

* IsNumber flow script was not handling strings, but rather only “numerics”.

 **iOS client:**

* Added barcode scan to grid detail view. Scanning from grid is available now.


---

# 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://help.novacuraflow.com/release-information/flow/6.13/6.13.11.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.