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

The Email component allows the creation of content in AEM that is then delivered as emails via Campaign Classic. The Core Email Component:

• is based on the Core WCM Component which supports Editable Templates and the Style System.
• provides 10 email-optimized production-ready components (Page, Container, Title, Text, Image, Button, Teaser, Experience Fragment, Content Fragment, Segmentation).
• provides advanced personalization and segmentation, thanks to the insertion of Campaign variables on most dialog fields, and to the flexible Segmentation component.
• provides optimal email-friendly HTML output, thanks to the CSS styles inliner, the HTML attribute inliner, and the HTML sanitizer.
• allows the creation of the emails anywhere.

You can now configure Adobe Experience Manager Assets to restrict the type of assets that users can upload based on the MIME type.

Adaptive Forms wizard: AEM Forms provides business user friendly wizard to quickly author Adaptive Forms. The wizard has a quick tab navigation to easily select pre-configured template, styling, fields, and submission options to create an adaptive form. This release brings following improvements to the wizard:

• Select or deselect fields: The wizard lets you create an Adaptive Form based on JSON and Form Data Model schemas. You can now select subset of fields within a schema to include in an Adaptive Form. The selected fields are converted to corresponding Adaptive Form data capture components to quickly create the desired adaptive forms.

• Use Static Templates: Customers with existing investments in legacy static templates can continue their journey of cloud adoption by using static templates in wizard to author adaptive forms. This provides additional time to customers to migrate old static templates to modern editable templates.

Remove hidden fields from a Document of Record (DoR) while server-side processing: You can generate the document of record PDF for end users containing only those fields which were visible to them during data capture experience. Upon form submission, the server validates which fields were hidden to the user based on submitted data and excludes from document of record for consistency.