> For the complete documentation index, see [llms.txt](https://docs.apica.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apica.io/platform-docs/zebratester-scripting/apica-data-repository-adr-aka-apica-table-server/apica-data-repository-release-notes.md).

# Apica Data Repository Release Notes

## V1.4 Release Notes (Dec 02, 2021) <a href="#apicadatarepositoryreleasenotes-v1.4releasenotes-dec02-2021" id="apicadatarepositoryreleasenotes-v1.4releasenotes-dec02-2021"></a>

* Releasing as a standalone package (before it was delivered along with ZebraTester)
* Tables are saved as encrypted files, means not as plain CSV files
* Supports Search option by a keyword on the created tables

## V1.3 Release Notes (April 22, 2021) <a href="#apicadatarepositoryreleasenotes-v1.3releasenotes-april22-2021" id="apicadatarepositoryreleasenotes-v1.3releasenotes-april22-2021"></a>

* Support for
  * client certificate authentication when communicating to ATS API end points. (refer section 1.2 for more details)
  * Supports new API end point for query table based on column names and values like below example GET url - [http://127.0.0.1:8992?cmd=ats\_retrieve\_row\_by\_column](http://127.0.0.1:8992/?cmd=ats_retrieve_row_by_column) body JSON- { "TableName”: "table\_name", "MatchColumnNames": \["column\_name1",”column\_name2”], "MatchColumnValues" : \["column\_value1","column\_value2"] } This API should also support retrieval based on multiple column names and values. This API also supports an optional input OutputColumnNames, the column names in a row to be retrieved based on the matching column names and values.
  * Supports the user case of not removing the retrieved column value from the table when querying based on the row index.

## V1.2 Release Notes (January 17, 2021) <a href="#apicadatarepositoryreleasenotes-v1.2releasenotes-january17-2021" id="apicadatarepositoryreleasenotes-v1.2releasenotes-january17-2021"></a>

* Support for
  * Authentication using a username and password, Authorization with the help of Users - Groups - Tables relations.
  * Create a New Table option, so that the user can create new tables that will be automatically added to the groups, the user belongs to.
  * Fixed bugs related to intermittent issues - duplicate retrieval and insertion of data.

## V1.1 Release Notes (September 30, 2020) <a href="#apicadatarepositoryreleasenotes-v1.1releasenotes-september30-2020" id="apicadatarepositoryreleasenotes-v1.1releasenotes-september30-2020"></a>

* Support for
  * Column actions like insert value at the start, append a value to the end, insert a column, and delete a column.
  * Row actions like editing a row; modifying the values of the columns inside a row or delete a row.
  * Server-side pagination for the ATS tables, so that table with a huge amount of data will load in milliseconds.
* Enable /Disable API Access
  * If disabled, the APIs supported by ATS won’t be reachable.
* Added a new API call for getting the size of a table on ATS.

## V1.0 Release Notes (July 20, 2020) <a href="#apicadatarepositoryreleasenotes-v1.0releasenotes-july20-2020" id="apicadatarepositoryreleasenotes-v1.0releasenotes-july20-2020"></a>

* Import CSV files
  * Contents of the CSV files will be stored as a table and can be viewed in the ATS GUI.
* Support Multiple tables
  * There’s an available drop-down for selecting a particular table.
* Export the selected table.
* Delete the selected table.
* REST endpoints can Retrieve and Upload data from/to ATS.


---

# 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.apica.io/platform-docs/zebratester-scripting/apica-data-repository-adr-aka-apica-table-server/apica-data-repository-release-notes.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.