> For the complete documentation index, see [llms.txt](https://docs.developers.symphony.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.developers.symphony.com/admin-guide/change-log/api-agent/archives/agent-20.14.md).

# Agent - 20.14

## Agent Download

{% hint style="info" %}
To download the Agent, click [here](https://storage.googleapis.com/sym-platform/developers/rest-api/agent-20.14.3.zip).

For a list of Agent x SBE compatibilities, click [here](/admin-guide/agent-guide/sbe-x-agent-compatibility-matrix.md).
{% endhint %}

## Agent Changes

### Agent 20.14.3

* A parentMessageId field is now exposed in the payloads returned by the Agent when retrieving information of a message consecutive of either a reply or a forward; it can be used as a link to the original message.

### Agent 20.14.2

* Message Update:
  * It is now possible to choose whether to update a message **silently** *(no notification for the user, no unread status)*, or instead to send the update as **unread,** particularly useful for **important** updates. In that later case, the user will view this update just as he would have viewed a new message *(unread chat status, notification, mention, activity feed, etc.).* Please refer to [Update Message](https://developers.symphony.com/restapi/v20.14/reference/update-message-v4) for more information.
  * Dependencies: Please note that this feature has dependencies on both **SBE 20.14** and a future **Client 2.0 release** (not communicated yet): this means that the feature is not necessarily available to you as soon as you install this agent version.
  * Following these changes, the Message Update API will be in General Availability (GA).
* Import message: It now possible to attach files when importing a message. See [Import Message](https://developers.symphony.com/restapi/v20.14/reference/import-message-v4) for more information.
* DLP: Improved scan of messages sent through the Agent to better support PresentationML / MessageML features.
* MessageML: Add support of the `language` attribute to the `<code>` tag, to adapt to each language specific display rules & syntax highlighting. See [Code](https://docs.developers.symphony.com/building-bots-on-symphony/messages/overview-of-messageml/messageml-basic-format-tags/text-level-formatting-and-semantics#tags) for more information.
* Elements: Add support for the selection of multiples items in the `Dropdown Menu` element. See [Dropdown Menu](https://docs.developers.symphony.com/building-bots-on-symphony/messages/overview-of-messageml/symphony-elements-1/dropdown-menu#attributes) for more information.
* Spring boot has been updated to version 2.6.6.

## **Deprecation Notice**

### **APIs**

* Datafeed v1: We plan to stop the support of Datafeed v1 service in the future. Please consider migrating your Bots to Datafeed v2 APIs, documented [here](https://developers.symphony.com/restapi/v20.14/reference/create-datafeed-v5).
  * In the future, the current Datafeed v1 APIs will transparently use the Datafeed v2 service to facilitate this transition period thanks to a bridge. This bridge will be introduced in the subsequent Agent release, June 2022.
  * However, migrating your bots to use the Datafeed v2 APIs is the only way to benefit from the improved reliability of the new Datafeed v2 service, which is more resilient to network issues and facilitates load balancing. You can benefit from a seamless migration to Datafeed v2 by leveraging the BDK in [Java](https://symphony-bdk-java.finos.org/) and in [Python](https://symphony-bdk-python.finos.org/).
  * More information are available for the [deprecation timeline and the introduction of the bridge](https://docs.developers.symphony.com/building-bots-on-symphony/datafeed) as well as the [benefits of Datafeed v2](https://developers.symphony.com/restapi/v20.14/reference/datafeed).


---

# 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.developers.symphony.com/admin-guide/change-log/api-agent/archives/agent-20.14.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.