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

When sharing digital assets as a link, the user can copy the URL to the clipboard right away. The enhancement lets you share assets in a faster and more convenient way. This functionality allows for faster and convenient asset sharing.

Figure: When sharing an asset as a link, you can now copy the URL to share it separately.

When you upload TXT files, the asset microservices automatically generate a thumbnail. The PNG thumbnail is a rendition of a TXT file that helps users identity the contents or the files to some extent, without opening the files. This functionality does not require any configuration and works by default.

Figure: A rendition of a TXT file is automatically generated to help you identify the file without opening.

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.

Automated Forms Conversion service can convert PDF Forms in Italian and Portuguese language to Adaptive Forms.

Acroform-based Document of Record: AEM Forms as a Cloud Service supports using Adobe Acrobat Form PDF (Acroform PDF) as a template for Document of Record besides XFA-based form template.

Microsoft® Azure data store connector: You can now connect Form Data Model to Microsoft® Azure Storage. It lets you retrieve and store adaptive form data to Microsoft® Azure Storage as a BLOB.

Use Adobe Sign roles in an Adaptive Form – Adobe Sign for business and enterprise service levels can 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 via 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 AEM Forms with Microsoft® Dynamics and Salesforce.com – The service provides out of the box data source configuration and data models for Microsoft® Dynamics and Salesforce.com. This makes it faster and easier for developers to configure Microsoft® Dynamics and Salesforce.com as data sources for an adaptive form.

New Category Picker UI for improved user experience, increased efficiency, and better support for complex product catalog

Better A11Y support for CIF Core Components

Cloud Service customers can now view Service Level Agreement (SLA) reports in Cloud Manager. This is going to be made available progressively over the next few months.
See SLA Reporting.

The type and severity of the IndexType and IndexDamAssetLucene quality rules has been changed. These are now both Bugs of Blocker severity.

New Oak index quality rules have been introduced to cover asynchronous and Tika configurations.

Increase max SSL certs per program to 50.

Self-service capability to allow users to create and manage multiple repositories by way of the Cloud Manager UI.

SonarQube was unnecessarily reading Git history data. On large code bases, this could lead to an unnecessary build performance penalty.

There is now an API available to invalidate the Maven dependency cache per pipeline.

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

Update Available status should not appear when the latest release is less than the current release.

Initial onboarding was failing for new organizations with long names.

Occasionally, when a pipeline is triggered twice for some reason, it results in one of the executions failing with a cannot update pipeline execution status error.

Sometimes, not all users were migrated to the target instance. To get this fix, CTT v1.5.6 is required along with aem-ethos-tools 1.2.354 or later version on the target AEM as a Cloud Service instance.

The Stop Ingestion button was being disabled during ingestion to the Publish instance. This is not necessary because there is no mongo restore step during Publish ingestion.

CTT did not clean up the /tmp directory after a successful extraction. This sometimes led to disk space issues.