Upload assets upload-assets
AEM Desktop App users with rights to add assets can add assets (such as images, documents, videos, or other media).
Edit assets and upload updated assets to Experience Manager edit-assets-upload-updated-assets
Open assets for editing when you want to make changes and upload the updated assets to the Experience Manager server. To avoid conflicts with edits of other users, use the app to initiate an editing session. Before you start editing, ensure that the asset does not have a lock icon on it indicating that another user is editing the asset.
To edit an asset, search for the asset or browse to the asset鈥檚 location. Click
Use Toggle Check-out to lock the asset to prevent conflicts with edits of other users in both the following situations:
- You鈥檝e started editing an asset without checking it out first (say by just opening it).
- You intend to start editing an asset soon and do not want others to edit.
Once you鈥檙e done making the edits, the app displays the Edited Locally status for the changed assets. All the changes saved to the assets are local-only until you upload the changes to Experience Manager. To upload an individual or a few assets one-by-one, click Upload Changes from the options for an asset. It creates a version of the asset in Experience Manager. Using the Web interface of Assets, you can see asset history in the Timeline view.
For best practices around collaborative editing, see Advanced workflow: collaborate on the same files and avoid editing conflicts.
In the following cases, you may want to discard your changes and edits to the local asset. Click Discard Changes.
- If you do not want to save your changes locally in Experience Manager.
- Start making changes on the original asset after saving some changes.
- Stop editing the asset as it is no longer needed.
If necessary, toggle check-out. The updated asset is removed from the local cache folder and is downloaded again when you edit or open it.
Upload and add new assets to Experience Manager upload-and-add-new-assets-to-aem
Users can add new assets to the DAM repository. For example, you may be an agency photographer or contractor who wants to add a large number of photos from a photoshoot to the Experience Manager repository. To add new content to Experience Manager, select
You can upload folders or individual files from your local file system. A folder鈥檚 hierarchy is preserved when it is uploaded. Before uploading assets in bulk, see Bulk uploads.
To view the list of assets transferred in a given session, click View > Assets transfers. The list allows you to view and quickly verify the file transfers of the current session.
You can control the upload concurrency (acceleration) in Preferences > Upload acceleration setting. More concurrency typically gives faster uploads, but can be resource-intensive, consuming more processing power of the local machine. If you experience a slow system, re-attempt uploads using a lower value of concurrency.
Bulk upload assets bulk-upload-assets
Users or organizations, such as photographers or creative agencies, can create numerous local assets during activities like photoshoots, retouching, or selecting from a larger set. These tasks are often done outside of Experience Manager. They can upload these large local folders to Assets directly from the desktop app. The folder hierarchies are preserved and all the nested sub-folders and included assets are uploaded. The uploaded assets are immediately available to other users of the same server for consumption as well. Assets are uploaded in the background, so the operation is not tied to a Web browser session.
After uploading, if the expected changes are not reflected in the app, click the refresh icon
Next Steps next-steps
-
Watch a video to get started with 51黑料不打烊 Experience Manager Desktop App
-
Provide documentation feedback using Edit this page
-
Contact Customer Care