Skip to main content

Desktop Experience

Towards a proper desktop experience. Getting an asset out of a DAM should not have to interrupt the work you opened it for. Find it in the portal, download it, find the download, open your editor, save a revision, then return to upload it: each hand-off is another chance to lose track of the right file.

Sambafied is being built around a more connected Windows workflow: an AEM work folder in File Explorer, with assets available to the applications you already use. The goal is less file shuffling, not less visibility into where your work is saved.

This page describes the intended experience and what to check in the Windows development preview. Application compatibility, uploads and recovery need confirmation for your build and AEM environment. It is not a production-readiness promise.

From an AEM asset to a Photoshop edit​

Imagine updating a campaign PSD stored in AEM. Instead of creating another download to keep track of, start with the connection's managed work folder.

  1. Find the right original. Open the work folder in Windows File Explorer and check that it belongs to the intended AEM connection. A listed file may still be cloud-only; seeing its name does not mean its contents are already on this PC.
  2. Open it in your usual application. Use the build's supported Open or Edit action and wait for the original to download. The intended folder experience also lets you reach assets through an application's file dialog. Check this with a small test asset before depending on a particular Photoshop workflow.
  3. Make and save your change. Save the managed working copy in the editor. A successful local save protects that local revision; it does not prove that AEM has received it.
  4. Review and upload deliberately. Return to Edited locally, check the saved copy and use Upload Changes when ready. Follow any checkout requirements separately. Do not assume that saving in an editor automatically uploads or checks the asset in.
  5. Verify the server result. Inspect Transfers and Operations, then confirm the intended revision in AEM. Where processing is required, check that separately from the binary transfer. Only then treat the change as available from the server.

For the detailed actions, see opening and editing, native work folders and transfer results.

Bring the asset into the work, not another download folder​

The same idea applies when placing an image in a layout or opening a file from an application's Open dialog. A connected folder should make the asset easier to reach without downloading the entire repository first.

Whether an application embeds a copy, keeps a link or supports a drag gesture depends on that application and your build. Check which file it uses and whether the original is locally available. Placing an image in a document does not mean edits to that document update the source asset in AEM.

Use the supported file picker or Open action if a gesture is unavailable. See creative application workflows before relying on a particular editing or placement path.

Know which state your work is in​

Keep these states separate when evaluating the workflow:

  • Listed remotely: the asset is visible, but its original may still need downloading.
  • Available locally: the original can be opened on this PC; offline availability still needs checking.
  • Edited locally: a newer save exists on this PC and may not have been uploaded.
  • Transferring: work is in progress, not yet a confirmed server update.
  • Confirmed in AEM: the intended revision is present on the server; any required processing or publishing is a separate check.

These are workflow distinctions, not a promise of identical badges in every build. If a transfer fails or its result is unknown, preserve the local file and inspect the details before retrying. A cancelled request may already have completed on the server. A newer local save can also remain unuploaded after an earlier revision finishes transferring.

See conflicts and recovery when the local and server copies no longer agree.

Make copies intentionally​

Sometimes a separate copy is exactly what you want: a new campaign variation, an export for delivery or an independent local experiment. Use Save As or export deliberately, choose its destination and keep a clear name.

An exported copy outside the managed work folder is independent of the connected asset. Editing it does not update the original in AEM. If you want it in the DAM, use the supported upload workflow and review the target folder, filename and collision choice. Do not use private cache folders as an import shortcut.

The distinction matters: editing a connected working copy and creating a new asset are different tasks. See uploading files and folders.

Keep the browser for the work it does well​

The aim is not to replace every AEM screen. Use AEM's browser interface for the metadata, approvals, permissions, publishing and other governance tasks your organisation manages there. Use the desktop workflow for reaching originals and working in native applications, then verify the resulting asset in AEM.

Browser actions explains how to keep the connection and asset destination clear when switching between them.

Try the workflow with a small test asset​

Start with the build-specific instructions and disposable test assets, not the only copy of important work. Follow Testing with OnPrem or Testing with SaaS for setup, expected outcomes and reporting. Check download, local save, upload, server revision and any processing as separate observations.

The PSD story is a workflow to evaluate, not evidence that every creative application or AEM environment has passed. Keep your build's readiness and limits alongside the results.