Please look at the Client 2.0 release notes to see which features have been introduced in the new Client.

• With Symphony v20.5, the usage of cards with Symphony Elements became possible. For more information, refer to Content Grouping and Interactive Elements Forms.

• Now, in read-only rooms, Symphony Elements appear disabled for non-owner users (those with read-only permission).

• Import Message V4: Fixed an issue where imported messages were showing the wrong timestamp input.

Desktop interop - August 2022

• Support of Glue42 & Finsemble platforms

• Support of StartChat intent (inbound)

• Support of ViewInstrument intent (outbound)

• Support FDC3 action buttons that can raise custom predefined intents (outbound)

Learn more on desktop interop .

Please look at the Client 2.0 release notes to see which features have been introduced in the new Client, such as features for Extension Apps, or eventual Elements changes. Some of them are documented below:

• Extension API: it is now possible to add a default value to the

• Fixed display bugs of Elements: removed extra spacing at the bottom of forms, as well as more general bugs

In the following subpages, you can find the archived Client 2.0 extensibility change logs.

Desktop interop - October 2022

• View Messages (inbound): You can now display in Symphony a view that aggregates all the messages that contain a specific #hashtag or $cashtag (new ViewMessages intent). See the View Messages section for more information.

• Support of FDC3 2.0: With the new FDC3 2.0 standard, intents can now return values to the calling app. As a result, the StartChat intent now returns the stream IDs of the chats where the message has been posted. This means that you can target these rooms directly when sending a subsequent chat message (see the new Send Chat Message intent below).

• Send Chat Message intent: You can now send a chat message to an existing chat, using its stream ID. Note: The user still needs to confirm the sending of the message. See the section for more information.

Important: As we add support for new intents in Symphony, please keep the Symphony app directory entry in your DIP up-to-date, as the desktop agent may block intents if they are not listed as supported by Symphony in the application directory.

Refer to the for more information.

• Fixed an issue where tables sent by the API was not being displayed in conversation views.

• Fixed an issue when sending an invalid emoji via API was returning a random emoji instead of displaying the emoji error.

• Fixed an issue with the rendering of tables within modals of forward and reply messages when using the Dark Mode theme.

• 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.

• Extension APIs:

  • Main functionalities of Extension Applications are supported in the version 20.9 in the Client 2.0.

  • Fixed missing refresh when a module is popped out

  • Fixed permission to allow again Applications to propose download of files to the end users

• New features for Symphony Elements:

  • Expandable card: new Expandable card with updated display. The card can have three different states, that can be set by the developer: collapsed, expanded but cropped, fully expanded. See how to use the expandable-card tag in specifications.

  • Label: it is now possible to set a Label associated with an element (text-field, masked text-field, textarea, dropdown, person selector) so the user can understand better the field meaning. This way the placeholder can focus on providing a hint of the expected format.

• Fixed display bug for Elements Buttons with a long text

• Fixed display of the placeholder for Elements Dropdown

• Fixed display bug for Cards

• Fixed display when Elements are focused in Client 2.0

• Minor fix on Elements (formreplies rendered after bookmark).