> For the complete documentation index, see [llms.txt](https://docs.truedat.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.truedat.io/v6.13/release-notes/v5/v5.9.md).
# v5.9
## Release highlights
### 1. Data Quality: Search for implementations filtering by quality rule fields
In the quality implementations lists you can filter by fields from the quality rule template they are linked to.
For example, you can define the quality owner at quality rule level but then want to get a list of all the implementations of a certain quality owner. The quality owner is informed in the quality rule template but you can go to the implementations screen and in the filters list you will see "quality owner" and that will return all the implementations linked to rules with the owner you are filtering by.
\
Features and fixes delivered with this release
----------------------------------------------
### Features
* TD-4260 As a data quality user I want to use quality rule fields as filters in the quality implementations list
* TD-5770 Postgres SSL connection
### Fixes
* TD-5716 Cannot save implementations with operators "is/is not equal to field" when the second field is from a reference dataset
* TD-5577 Users with just the default role cannot see global saved filters nor save filters
---
# 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://docs.truedat.io/v6.13/release-notes/v5/v5.9.md?ask=&goal=
```
`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.