> 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.8.md).

# 6.13.8

Released 2021-04-21

**MSSQL database connector:**

* Improved performance: MSSQL queries can become very slow in combination with using Flow variables. Added support for specifying a SQL type on the flow variable like: @MyVariable#VARCHAR

**Rest connector:**

* Deselecting output in REST Connector no longer leads to a crash
* Input fields with & in the name are not replaced with underscore
* Fix for floating-point numeric input from “wrong culture”

**Flow studio:**

* Resolved problems with user custom properties in application packages during runtime

**Workflow engine:**

* Fixed an error regarding variables not being resolved correctly with grid row & cell item styling when coming back from a paused state

**Server Tool:**

* Import is more OS agnostic. Added a dbonly flag so it is possible to import/export only databases (without the associated files)


---

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