Skip to main content

Creating and Restoring an Asset Version

Unlike Pages, Asset versioning does not happen often; neither manually or via our SOI Request for Activation workflow process. Rather, versioning typically occurs when a user uploads an asset to the same directory in the DAM where the asset's filename is an exact match to one that already exists.

The Name Conflict popup is the typical way users will get a versioned asset. Manually-creating an asset version instructions are similar to page versions, and are documented below.

Asset Overwriting

If a user uploads an asset to a directory where the same filename exists, the user will be prompted for an action to take on the asset:

  • Cancel: Cancels out of the current action, stepping the user back.
  • Keep Both: Both assets are kept, and the newest one being uploaded will be appended with a numeric. If a copied version already has a numeric, it is incremented by 1 until a valid filename is allowed. (ie: animals1.jpg matching would cause the uploaded file to be renamed to animals2.jpg). Asset Metadata is untouched for the two files.
  • Replace: The current file on AEM is replaced with the file you are uploading. Asset metadata is only kept for the new file uploaded, as the previous file is lost.
  • Create Version: The current file on AEM is kept, being updated with the newest document changes from your uploaded file. Asset Metadata is unchanged from the previous version in this instance.

Creating an Asset Version

Hard select the asset that you want to create a version of and Navigate to Create > Version.

Add the proper "Label/Comment" and click on Create.

Reverting to a Previous Asset Version

Within AEM Assets, ensure the view is in "Timeline" mode instead of "Content Only".

Hard-select the asset you want to view the Timeline for.

Click on the version that you want to restore and Select Revert to this Version.

*Note: You may also Preview the version selected for a given asset. You may re-label and/or add a comment to the asset version selected as well.

No visible notification will occur when the process completes.

Noting the Timeline view, the Asset will get versioned before reverting, and kicks off an Asset Re-Processing workflow.