Current Release Notes for Adobe Experience Manager as a Cloud Service release-notes

Users can now sort the assets displayed in the search results in Column and Card views. The sorting works on Name, Created, Modified, or None columns.

Figure: Sort the search results in Assets in Column and Card views.

To programmatically invoke processing using asset microservices, a new API is introduced. Developers can now apply an existing folder-level processing profile on one or more specific assets in a folder. The processing profile gets applied based on custom metadata properties updates. See AssetProcessor in the Experience Manager API reference. As before, it is possible to use asset microservices from the user interface.

Use Adobe Sign roles in an Adaptive Form – Adobe Sign for business and enterprise service levels let you optionally expand the roles for Agreement recipients, beyond just the Signer, to better match their workflow requirements. You can now enable each recipient of the agreement to configure their role in an Adaptive Form, with Signer being the default role.

Analytics for Adaptive Forms – You can now capture and track end-user behavior by way of Adobe Analytics for Adaptive Forms to gather end-user insights. It helps make informed decisions based on data to improve the end-user experience.

Easily connect Adobe Experience Manager (AEM) Forms with Microsoft® Dynamics and Salesforce – The service provides out-of-the-box data source configuration and data models for Microsoft® Dynamics and Salesforce. This makes it faster and easier for developers to configure Microsoft® Dynamics and Salesforce as data sources for an adaptive form.

E-Sign an adaptive form using DocuSign – You can use DocuSign to e-sign an adaptive form. The service provides a custom submit action to use DocuSign with an adaptive form. You can install the package available on Software Distribution to import the submit action.

Unified Storage Connector – Use Unified Storage Connector to externalize in-process data in customer-managed repositories. For example, you can

• Enable Forms Portal’s save and resume functionality and store adaptive forms drafts in a customer-managed data repository.
• Store in-process AEM Workflows data (AEM Workflow Variables data) that contains Sensitive Personal Data (SPD) in a customer-managed repository.

AEM Forms as a Cloud Service - Communications – Communication APIs help you combine XDP templates and XML data to generate print documents in various formats. The service lets you generate documents in synchronous mode. The APIs enables you to create applications that let you:

• Generate documents by populating template files with XML data.
• Generate output forms in various formats, including non-interactive PDF print streams.
• Generate print PDF files from an XFA form PDF and Adobe Acrobat Form.

The new “associated commerce content” tab in AEM Sites editor increases author efficiency by quickly getting access to relevant AEM product content for the current context

Improved product picker UI for better user experience, increased efficiency, and support for complex product catalog

Respect “include_in_menu” property in navigation component

Menu cache flush is not working as expected

JS errors during the AEM CS deployment step and when not using client-side components

Cannot create CIF cloud config in folders that have a sling:configs node

Screens as a Cloud Service now supports basic playback monitoring. The player now reports various playback metrics with each ping (defaults to 30 seconds). Based on the metrics, it can detect various edge cases (stuck experience, blank screen, scheduling problem, and so on). This feature lets the team remotely monitor if a player is properly playing content. It improves reactivity to blank screens or broken experiences in the field, and decreases the risk of showing a broken experience to the user.
See Basic Playback Monitoring for more details.

Thumbnail Support for videos in now supported in Screens as a Cloud Service. A content author can define a thumbnail for videos so that the image is used as a placeholder and properly test content playback and targeting, while the actual video is being finalized by the appropriate team. The image can also be used in case the playback of the video fails.
See Thumbnail Support for Videos for more details.

The player could not show content from the Embedded page and this issue is now fixed.

After a successful login, navigating to the default page (channels) ended up in an Internal Server Error page.

Associated tag entries were not removed when removing playlists.

The version of the AEM Project Archetype used by Cloud Manager has been updated to version 30.

The program cards on the Cloud Manager landing page and the associated experience have been refreshed.

The Code Quality Step Log now includes verbose logging information on the OakPal scanning process.

The Activity page menu options now include an option to Download Log for completed Code Generator executions. Selecting this downloads the log of the build step.

Clicking directly on the Program card now navigates to the Cloud Manager Overview page.

Users now see a more comprehensible message when trying to add an IP allowlist in a program that has reached the maximum allowed number of IP allowlists that can be configured.

The wrong URL was copied when selecting the copy URL menu option from the Repositories screen.

Improved User Mapping with a simplified User Experience, including the following features listed below. For more details, see Using User Mapping Tool.

• Test connection to the User Management API before running the User Mapping
• Gracefully skip errors and continue with the User Mapping activity
• User Mapping no longer fails if the Access Token expires (after 24 hours). User Mapping can be rerun from where it last stopped.

To increase CTT robustness, content can be ingested to either Author instance or Publish instance at a time.

When versions are included, the path /var/audit is automatically included to migrate audit events.

Ability to detect and report on total node count.

Ability to detect and report on the node store type and size.