ÃÛ¶¹ÊÓƵ

Manage the assets centrally in Experience Manager Assets.

Access the assets in any native desktop applications, including third-party applications and in ÃÛ¶¹ÊÓƵ Creative Cloud. While doing so, users can easily adhere to the various standards including branding.

Make sure that your Experience Manager version is compatible with the Experience Manager desktop app.

Download and install the application. See install desktop app below.

Test the connection using a few assets. See how to browse and search for assets.

Launch the application on logon.

Show a window when the application starts.

Cache Directory: Location of the local cache of the app (it contains the locally downloaded assets).

Network Drive Letter: The drive letter used to map to the Experience Manager DAM. Do not change this network drive letter if you are not sure. The app can map to any drive letter on Windows. If two users place assets from different drive letters, they cannot see the assets placed by each other. The path of the assets change. The assets remain placed in the binary file (say INDD) and are not removed. The app lists all the available drive letters and by default uses the last-available letter that is typically Z.

Maximum Cache Size: Allowed cache on hard disk in GB that is used for storing locally downloaded assets.

Current cache size: Storage size of the locally downloaded assets. The information is displayed only after assets are downloaded using the app.

Automatically download linked assets: When you download the original file, assets placed in supported native Creative Cloud apps are automatically fetched.

Maximum number of downloads: Change with caution. When downloading assets for the first time (via Reveal, Open, Edit, Download, or similar option), the assets are downloaded only if the batch contains less than this number. The default value is 50. Do not change if you are unsure. Raising the value can result in longer wait times, while lowering it might prevent you from downloading all necessary assets or folders in one attempt.

Use legacy conventions when creating nodes for assets and folders: Change with caution. This setting lets the app emulate v1.10 app behavior when uploading folders. In v1.10, the node names created in the repository respect the spaces and casing of the folder names provided by the user. However, in v2.1 of the app, the extra spaces in the folder names are converted to dashes. For example, uploading New Folder or new folder creates the same node in the repository if the option is not selected and the default behavior in v2.1 is retained. If this option is selected, then different nodes are created in the repository for the above two folders and it matches the behavior of the v1.10 app.

The default behavior of v2.1 remains unchanged: it replaces multiple spaces in folder names with dashes in the repository node name and converts node names to lowercase.

Upload Acceleration: Change with caution. When uploading assets, the application can use concurrent uploads to improve upload speed. You can increase the concurrency of the upload by moving the slider to the right. The slider on the far left-hand side means no concurrency (single-threaded upload), the middle position corresponds to ten concurrent threads, and the maximum limit on the far right-hand side corresponds to 20 concurrent threads. A higher concurrency limit is more resource-intensive.