Adobe Experience Manager (AEM) Assets can identify if an uploaded file contains references to assets that already exist in the repository. This feature is available for supported file formats only. If the uploaded asset contains any references to AEM assets, a bidirectional link is created between the uploaded and referenced assets.
Besides eliminating redundancy, referencing AEM assets in Adobe Creative Cloud applications enhances collaboration and increases the efficiency and productivity of users.
AEM Assets supports bidirectional referencing. You can find referenced assets in the asset detail page of the uploaded file. In addition, you can view the referencing files for AEM assets in the asset details page of the referenced asset.
References are resolved on the basis of path, document ID, and instance ID of the referenced assets.
You can reference existing AEM assets from within an Adobe Illustrator file.
Using AEM desktop app, mount AEM Assets repository as a drive on your local machine. Within the mounted drive, navigate to the location of the asset that you want to reference.
Drag the asset from the mounted drive to the Illustrator file.
Save the Illustrator file to the mounted drive, or upload to the AEM repository.
After the worflow completes, go to the asset details page for the asset. The references to existing AEM assets are listed under Dependencies in the References column.
The referenced assets that appear under Dependencies can also be referenced by files other than the current one. To view a list of referencing files for an asset, click the asset in the under Dependencies.
Click the View Properties icon from the toolbar. In the properties page, the list of files that reference the current asset appear under the References column in the Basic tab.
To reference AEM assets from within an InDesign file, either drag AEM assets to the InDesign file or export the InDesign file as a ZIP file.
Referenced assets already exist in AEM Assets. You can extract subassets by configure InDesign server. Embedded assets in an InDesign file are extracted as subassets.
If the InDesign server is proxied, InDesign files have their preview embedded within their XMP metadata. In this case, thumbnail extraction is not explicitly required. However, if the InDesign server is not proxied, thumbnails must be explicitly extracted for InDesign files.
This procedure is similar to Adding AEM assets as references in Adobe Illustrator.
Using a WebDav client, mount AEM Assets as a drive.
To create references to AEM assets in a Photoshop file, navigate to the corresponding assets in the mounted drive using the Place linked functionality in Photoshop.
Save in Photoshop file to the mounted drive or or upload to the AEM repository.
After the workflow completes, the references to existing AEM assets are listed in the asset details page.
To view the referenced assets, close the Rail in the asset details page.
The referenced assets also contain the list of assets they are referenced from. To view a list of referenced assets, navigate to the asset details page and close the rail.
The assets within compound assets can also be referenced based on their Document ID and Instance ID. This functionality is available with Adobe Illustrator and Adobe Photoshop versions only. For others, referencing is done on the basis of relative path of linked assets in the main compound asset as done in earlier versions of AEM.
For the supported assets with multi-page formats — PDF files, AI files, Microsoft PowerPoint and Apple Keynote files, and Adobe InDesign files — AEM can generate subassets that correspond to each individual page of the original asset. These subassets are linked to the parent asset and facilitate multi-page view. For all other purposes, the subassets are treated like normal assets in AEM.
Subasset generation is disabled by default. To enable subasset generation, follow these steps:
To generate the subassets do one of the following:
New assets: The DAM Update Assets workflow executes on any new asset that is uploaded to AEM. Subassets are auto-generated for new multi-page assets.
Existing multi-page assets: Manually execute the DAM Update Assets workflow following either of the steps:
alt + 3. Click Start Workflow, select DAM Update Asset, click Start, and click Proceed.
Specifically for Microsoft Word documents, execute the DAM Parse Word Documents workflow. It generates a
cq:Page component from the contents of the Microsoft Word document. The images extracted from the document are referenced from the
cq:Page component. These images are extracted even if subasset generation is disabled.
The subassets are displayed only if the subassets are generated and are available for the selected multi-page asset. To view the generated subassets, open the multi-page asset. In the upper-left area of the page, click and click Subassets from the list. When you select Subassets from the list. Alternately, use the keyboard shortcut
alt + 5.
You can view a multi-page file, such as PDF, INDD, PPT, PPTX, and AI file, using the Page Viewer feature of AEM Assets. Open a multi-page asset and click View Pages from the upper-left corner of the page. The Page Viewer that opens displays the pages of the asset and the controls to browse through and zoom each page.
For InDesign, you can extract pages using InDesign server. If the previews of pages are saved during InDesign file creation, then InDesign Server is not required for page extraction.
The following options are available in the toolbar, in the left rail, and in the Page Viewer controls:
Desktop Actions to open or reveal a specific subasset using AEM desktop app. See how to configure Desktop Actions if you are using AEM desktop app.
Properties option opens the Properties page of the specific subasset.
Annotate option allows you to annotate the specific subasset. The annotations you use on separate subassets are collected and displayed together when the parent asset is opened for viewing.
Page Overview option displays all the subassets simultaneously.
Timeline option from the left rail after clicking displays the activity stream for the file.