ÃÛ¶¹ÊÓƵ

No, only approved and latest version of the assets are available for search and delivery using Dynamic Media with OpenAPI capabilities, ensuring brand consistency across all channels and applications.

The status of an asset in Experience Manager Assets is governed by jcr:content/metadata/dam:status property. The values of this property can be:

• Approved

• Rejected

• Changes requested

Experience Manager Assets distinguishes Approved status using an approved icon available on the asset card, as depicted in the following images for Admin and Asset views:

Admin view

Assets view

To approve all assets in a folder, see instructions on how to bulk approve assets in a folder. There is also a video that depicts the entire process.

After setting up a folder for bulk approval, all new assets that are added to the folder are approved automatically. All existing assets are approved after reprocessing assets. See Reprocessing digital assets for instructions on how to reprocess assets. If you copy or move unapproved assets from any other folder, you need to reprocess the assets.

The asset is marked as Rejected, if the administrator specifies Rejected or Changes requested values. Experience Manager Assets distinguishes the Rejected status using available on the asset card in Admin view.

Similarly, Experience Manager Assets distinguishes the Rejected status in Assets view using the following Rejected status on the asset card:

Users requiring access to Experience Manager Author environment are managed as ÃÛ¶¹ÊÓƵ IMS users in ÃÛ¶¹ÊÓƵ’s Admin Console. For information about what ÃÛ¶¹ÊÓƵ IMS users are, and how they are accessed and managed in Admin Console, see ÃÛ¶¹ÊÓƵ IMS users.

Yes, you can approve multiple assets within a folder simultaneously.

Execute the following steps to approve multiple assets simultaneously in Experience Manager Assets Admin view:

1. Select the asset(s) and click Properties.
2. In the Basic tab, scroll down to Review Status.
3. Change the review status to Approved.
4. Click Save & Close.

Similarly, to approve multiple assets simultaneously within a folder in Assets view:

1. Select the asset(s) and click Bulk Metadata Edit.

2. Select Approved in the Status field available in the Properties section in the right pane.

3. Click Save.

Central asset governance in Experience Manager allows the DAM Administrators or Brand Managers to manage access to assets. They can restrict the access by configuring roles or by setting activation and deactivation time for approved assets on the authoring side, specifically on the AEM as a Cloud Service author instance.

End-users searching or utilizing delivery URLs can gain access to restricted assets upon successfully passing the authorization process.

For more information, see Restrict access to assets in Experience Manager.

As a DAM user, you might not have permissions to approve assets. To get the permissions to edit the approval status of an asset, the administrators can edit the default or any other metadata schema applied to the asset folder to provide edit permissions to the Review Status field. For more information, see how to disable edit for the Review Status field.

Dynamic Media with OpenAPI capabilities and Dynamic Media represent distinct solutions, each offering its specialized delivery capabilities. It is imperative to thoroughly review your specific requirements to determine the most fitting solution that aligns with your needs.

General guidance from ÃÛ¶¹ÊÓƵ is to leverage Dynamic Media with OpenAPI stack for any integration use cases (1st or 3rd party apps). If there already exists an integration with Dynamic Media stack, recommendation is to not change it as OpenAPI stack URLs are different in structure. Only for any net new integration use cases, leverage OpenAPI stack. If your use case requires advanced modifiers not available with OpenAPI stack, then avoid the OpenAPI stack until ÃÛ¶¹ÊÓƵ bridges the gap. Even for basic native delivery from AEM Assets Cloud Services, OpenAPI stack can be evaluated as long as your use case is covered with the modifiers available with OpenAPI stack. In conclusion, Dynamic Media and Dynamic Media with OpenAPI stack can co-exist, depending on the nature of your use case.

The following are some of the key differences between Dynamic Media with OpenAPI capabilities and Dynamic Media:

table 0-row-2 1-row-2 2-row-2 3-row-2 4-row-2 5-row-2 6-row-2 7-row-2 8-row-2 9-row-2 10-row-2 11-row-2
Dynamic Media with OpenAPI capabilities	Dynamic Media
Available only with Assets as a Cloud Service	Also available with On-premise or ÃÛ¶¹ÊÓƵ Managed Services with additional configuration and provisioning steps.
Limited set of supported image modifiers, such as width, height, rotate, flip, quality, and format	Rich set of available image modifiers
Restricted asset delivery based on users, roles, date, and time	Assets published to Dynamic Media are accessible to all users
Most developers are familiar with OpenAPI specifications. AEM Assets extensibility becomes really simple by using Micro-Frontend Asset Selector.	SOAP -based APIs, which become a barrier while developing integration customizations.
Any changes made to approved assets in DAM, including version updates and metadata modifications, are automatically reflected in the delivery URLs. With a short Time-to-Live (TTL) value of 10 minutes configured for Dynamic Media with OpenAPI capabilities via CDN, updates become visible across all authoring and published interfaces in under 10 minutes.	Recommended CDN TTL of 10 hours. You can override the TTL value using the cache invalidation action.
Only approved assets are available for asset delivery to downstream applications, enabling on brand approved assets in digital experiences.	Any updates to a Dynamic Media published asset are auto-published without any approval workflow, which does not ensure on brand approved assets in digital experiences.
Usage reports based on number of assets delivered. This feature will be available soon.	Usage reports are not available. This feature will be available soon.
Assets marked as Expired on Assets as a Cloud Service repository are not anymore available to downstream applications.	No inherent asset expiry. An asset remains public until it is deleted from AEM as a Cloud Service repository.
Does not support image presets and video smart crop capabilities.	Supports image presets and video smart crop capabilities.
Dynamic video encodes, that ensure best encodes are served based on the input video. No setup is required for native video delivery.	Standard 3 encodes irrespective of input video (can impact video delivery performance). You need to manually set up different encodes for different video bit rates.
Difficult to guess asset UID based URLs (enables URL obfuscation), but SEO optimized.	URL obfuscation only available for URL query parameters. Assets IDs (asset names) in URLs are recognizable.

The table below outlines the key differences between the two solutions:

table 0-row-2 1-row-2 2-row-2 3-row-2 4-row-2 5-row-2 6-row-2 7-row-2 8-row-2
Dynamic Media with OpenAPI capabilities	Connected Assets
Assets on the remote DAM deployment are available on AEM as a Cloud Service.	Assets on the remote DAM deployment can be available on AEM as a Cloud Service or ÃÛ¶¹ÊÓƵ Managed Services.
Asset binaries are not copied when assets on a remote DAM deployment are available an AEM Sites instance.	Asset binaries are copied when assets on a remote DAM deployment are available on an AEM Sites instance.
Support for all asset format types that are supported by AEM Assets.	No support for videos.
You can use Dynamic Media on the local Sites deployment while fetching assets from remote DAM deployment.	Dynamic Media on local Sites deployment is read-only.
No restrictions on the number of AEM Sites instances connected to a remote DAM deployment. You can restrict the access to assets on the Sites instance by configuring roles for approved assets on remote DAM.	Restriction to connect no more than 4 AEM Sites instances to the remote DAM deployment. Increased number requires additional testing.
Both Asset Selector and Dynamic Media with OpenAPI capabilities are extensible to allow custom integrations.	Connected Assets APIs are not extensible to allow custom integrations.
Any changes made to approved assets available on remote DAM deployment, including version updates and metadata modifications, are automatically reflected on the Sites instance within a short Time-to-Live (TTL) value of 10 minutes.	Asset updates on remote DAM deployment are handled via lifecycle events automatically but takes much more time as compared to Dynamic Media with OpenAPI capabilities.
Asset metadata on remote DAM is available on AEM Sites instance as well.	Asset metadata on remote DAM is not available on AEM Sites instance.