> 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/client-2.0-apis/archives/client-2.0-20.10.md).

# Client 2.0 - 20.10

This page describes the features introduced on Client 2.0 (20.10) version

* Symphony Elements:
  * Fixed display bug of Elements in Dark theme. Dark theme is not yet fully supported.
  * Fixed display bug of Elements in Condensed mode. Condensed mode is not supported.
  * Fixed display bug of Text area (incorrect font).
  * Fixed display bug of Tooltip (incorrect font & font color).
  * Text area: Fixed missing default value when a label is also set.
* Fixed security vulnerabilities in message rendering libraries
* Starting with Symphony v20.10, some “built in” applications of the Marketplace will also be modifiable directly in the Admin Portal. Please reach out to your Technical Account Manager for more information.
* Extension Applications:
  * Improved support of Client 2.0 (retrieve user entitlements, support of theme changed event, support of app in last active popped out workspace, support of developper mode, support of Module service open link, focus, and redirect methods)
  * Added an openIM functionality in the [UI Service](/ext-apps/overview-of-extension-api/extension-api-services/ui-service.md).


---

# 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://docs.developers.symphony.com/admin-guide/change-log/client-2.0-apis/archives/client-2.0-20.10.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.
