Adobe Experience Manager desktop app release notes release-notes-v2

Paths to placed files in the native application use a global desktop path (placed from the local network share shown with the Reveal option).

Paths are stored in the file’s XMP record by the native app.

Experience Manager has extracted the XMP record with the paths to the asset’s metadata record.

The paths can be matched to assets in Experience Manager, that is, the placed files are also in Experience Manager under a matching path.

Added Support for IMS login. IMS integration allows the desktop app to perform access token refresh automatically, allowing the user to stay logged in for up to 14 days.

Improved support for corporate proxies and web filtering.

The desktop app displays a session timeout error message when you click Sign In.

Issues while accessing desktop app v2.2.0 on macOS.

The desktop app displays an error message when you sort assets by clicking Edited Locally.

Support for Apple Silicon (M1).

Ability to remember the connection string while logging on to the desktop app.

The desktop app stops responding when you upload files in a folder that contains Chinese characters (ASSETS-9237).

desktop app replaces dots with dashes in file names (ASSETS-10955).

A new option to Clear Cookies is added to the main menu of the application. It helps with potential logon issues, for example when changing a connection from a server to another. See clear cookies before connecting.

A new option has been added that, if selected, allows the app to upload folders and files with node names in Adobe Experience Manager matching the local file and folder names. This process ensures consistency between local and uploaded names.

This behavior is similar to the default behavior in version 1 of the desktop app. Whereas in the current version, if the option is not enabled then whitespaces and the characters % ; # , + ? ^ { } " in folder names are replaced with dashes in folder paths. Also, the upper-case characters are converted to lower case in folder paths. However, in file names, the characters # % { } ? & are replaced with dash; but whitespaces and casing are retained. For more information see, app Preferences and Upload and add new assets.

Upload acceleration setting is now made available to boost the upload performance. When this setting is turned on, the app uploads faster by using more local CPU threads and is more resource-intensive.

Asset uploads when filenames or paths containing certain GB18030 characters is fixed.

Sort by relevance option is available after switching to another sort type in the search results.

The desktop app now lists sub-folders without the need for explicit refresh.

(Windows) Fixed a rare issue of unusable app interface on some Windows machines. Users cannot click on the app interface as it appears distorted with the click-area of interface elements ‘shifted’ sideway.

Allow option to configure %Temp% directory to match %APPDATA% path.

Allow users to log in on Experience Manager Author via Okta SAML authentication.

The application provides full control over operations that require full transfer of asset binaries from and to Experience Manager (Open, Edit, Upload Changes, and Upload Assets).

• If you want to work with the asset on desktop, you must explicitly Open, Edit, or Download to your desktop, either individually, in a folder, or via multi-selection.

• If you want to get local changes to assets uploaded to Experience Manager, you need to select Upload Changes, either individually or via multi-selection.

• The application is not a ‘sync client’ that synchronizes assets across the desktop and Experience Manager.

• The application does not provide a network share that maps the Experience Manager repository as a virtual folder structure.

The list of assets shown by the application is based on the status of the Assets repository. Files downloaded locally and subsequently renamed in the local files or cache folder are not displayed or managed with the application.

If the app does not display the expected results, click the refresh icon in the top bar.

The local network share, shown when you use Reveal File action, only shows files (and folders) that are available locally. Reveal File and Reveal Folder pre-downloads assets to help get the right assets showing in the local network share.

SMB (Mac) / WebDAV (Win) local network share is used when an Adobe Creative Cloud app reads the asset files linked / placed in a native file of the Creative Cloud app.

At times, the interface of the desktop app might become blank. Right-click and click Refresh to reload the application. After such a refresh, you start at the root of the DAM repository. Updates to or statuses of your assets are retained.

Difficult to navigate folders / search results without a track pad or mouse pointer. The scroll-bar does not appear with wheel-less mouse devices.

Infrequently, the progress bar does not display correctly when the uploading asset changes.

After applying and removing the filter to find all locally edited assets, the app does not take users to their search results or folder view that the users started with. The app displays the root folder of the DAM repository.

At times, when you connect to a URL that does not have an Experience Manager server running, the connect screen becomes unresponsive. Exit the application and start it again.

When uploading changes to an asset with comments, the comments are stored with the asset in Experience Manager but are not visible as versioning comments. This issue is resolved in Experience Manager 6.4.5 and Experience Manager 6.5.1. Adobe recommends installing the latest service packs.

A user cannot cancel asset transfers. If you triggered an unintended large transfer, exit the application and start it again.