AEM desktop app Release Notes
Adobe Experience Manager (AEM) desktop app
App version (Revision)
Supported AEM versions
AEM 6.5, AEM 6.4, AEM 6.3 (with compatibility package)
August 30, 2019 (Mac), September 9, 2019 (Win)
System requirements and prerequisites
AEM desktop app is compatible with the following operating systems:
- Mac OS X 10.10 or later, with latest bug fixes.
- Windows 7 and Windows 10 with the latest service packs and bug fixes.
The app works with the following AEM versions, whether deployed on-premise or on Adobe Managed Services (AMS):
- AEM 6.5.0 or later
- AEM 6.4.4 or later
- AEM 6.4.0 - 6.4.3 with compatibility package
- AEM 126.96.36.199 and later with compatibility package
- For AEM 6.3, no service packs are planned . Adobe recommends to upgrade to a later AEM version.
The version of the app you plan to install on your local machine requires a specific Adobe Experience Manager server version/additional server-side components (service packs, hot fixes, or feature packs). Contact your AEM administrator for help.
Support for different asset and file types
The application supports assets stored in AEM that represent binary file for its basic operations. Opening files in the native desktop application relies on the operating system association of the specific file types like PNG or JPG to specific applications like Mac Preview or Adobe Photoshop.
A few file types support placing linked assets in the binary. The application pre-downloads the linked assets if the asset is present in the AEM repository when such binary files are opened using the desktop app. Currently supported file types are:
- Adobe InDesign files (INDD format)
- Adobe Illustrator files (AI format)
- Adobe Photoshop files (PS format)
The feature is supported with Adobe Creative Cloud 2018 and Creative Cloud 2019 versions of the above application. The app uses a heuristic, best-match approach to map the local desktop paths of linked assets to URLs on the AEM server. It relies on a few assumptions:
- Paths to placed files in the native application use a global desktop path (placed from the local network share shown with “Reveal” option)
- Paths are stored in the file’s XMP record by the native app
- AEM has extracted the XMP record with the paths to the asset’s metadata record
- The paths can be matched to assets in AEM (meaning, the placed files are also in AEM under a matching path)
New features and enhancements
To know the details, see What's New in the App .
Important notes about how the app works
It is important to understand the following about the application and how it works.
- The application provides full control over operations that require full transfer of asset binaries from and to AEM (open, edit, upload changes, and upload assets).
- If you want to work with the asset on desktop, you need to 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 AEM, 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 AEM.
- The application does not provide a network share that maps the AEM repository as a virtual folder structure.
- The list of assets shown by the application is based on the status of the AEM Assets repository. Any files downloaded locally and then renamed in the local files or cache folder are not displayed or managed by the application.
- If the app does not display the expected results, click 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.
The following diagram illustrates the flow of assets and files from cloud to local file system and vice versa, as initiated by user actions.
User interface issues:
- At times, the interface of the desktop app might become blank. Right-click and click Refresh to re-load 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 might not appear with mouse devices without mouse wheel.
- 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 doesn’t have AEM server running, the connect screen becomes unresponsive. Exit the application and start it again.
CRUD (Create, Read, Update, and Delete) issues:
- Application tries to upload files even with invalid characters, might cause server-side upload failure.
- When uploading changes to an asset with comments, the comments are stored with the asset in AEM but are not visible as versioning comments. This issue is resolved in AEM 6.4.5 and AEM 6.5.1. Adobe strongly recommends installing the latest service packs.
- Asset transfers cannot be canceled by the user. If you triggered an unintended large transfer, exit the application and start it again.
- At times, on Windows, an asset's status may immediately change to Edited Locally after opening it, even though you may not have edited it. Click Refresh to update.