AEM as a Cloud Service 2022.8.0 release update

Transcript

Hi everybody, welcome to the Adobe Experience Manager or AEM August release overview. As usual, when it comes to these overviews, we like to organize the new features by the different value pillars that you see in front of you. All three of these value pillars work together to allow customers to deliver personalization at scale with Adobe Experience Manager. Starting with Content for All, this value pillar focuses all around empowering everyone to create content at scale. Everybody at your team can now be empowered when it comes to contributing to the different processes involved of delivering personalization to your end users. These features focus around making the process of getting involved easier and using the different features of AEM to empower people across your organization to get involved. Second, we have Experience Intelligence. This allows you to create data-driven experiences that are meaningful across any journey. So using automation, using artificial intelligence, really leveraging these features when it comes to creating these data-driven experiences. And finally, we have Agile Experience Delivery, which allows you to build faster and accelerate delivery of these connected experiences everywhere. When it comes to this release, so the August release, most of the features you see will focus around the Content for All pillar. Here is a quick look at the product releases that we are going to be covering today for the August product release overview. And starting with the value pillar that we’re going to see the most of today, it’s Content for All. So like I mentioned earlier, these features all focus around empowering everyone across your organization to create content at scale for your end users. And we’re going to start with AEM Forms. This cloud service pre-release feature, the selecting and deselecting wizard fields, focuses on improving the data screen within the wizard UI to allow for selecting and deselecting field options for the creation of your forms. With AEM Forms, organizations leverage master datasets or schemas to capture data. And the organization’s forms use these schemas to capture the data from the end user filling out form. The wizard UI uses these schemas as it builds out the forms that will be used by end users. With this feature, authors can leverage the wizard UI to quickly create adaptive forms while using a subset of fields from the master schema, but now have the support needed to select or deselect specific fields within the schema that are relevant to the specific form. This feature further simplifies the process of creating forms and enhances the wizard UI with more selection options when it comes to the form fields for the forms that the wizard UI will create. Continuing our focus of enhancing the wizard UI, we have also been working on offering additional support for static form templates within the wizard UI. With this additional support, customers can leverage their preferred static templates within the wizard UI. This feature provides more support and use of legacy static templates as the wizard UI now allows customers to use these static templates to author adaptive forms. So customers with legacy static templates can use them with the wizard UI to create adaptive forms and continue their journey of cloud adoption. Now customers have more options when it comes to the kinds of templates they want to leverage within the wizard UI. This also provides more runway and flexibility to migrate legacy templates to editable templates in the future. Customers will benefit from increased efficiency by expanding the type of content that is used to create adaptive forms, as more templates can be used to ultimately create more adaptive forms within the wizard UI. And as we can tell from the other features, we really keep working on advancing the wizard UI. This feature allows users to streamline the form creation process by being able to launch the wizard UI directly from the intended web page for the form that is being created. With these enhancements, users can now invoke the wizard UI directly from the page that the form will live on, which decreases the amount of time it takes for the form creation process, as forms previously had to be created separately and then embedded into the intended page. Now form practitioners can enjoy an improved content and forms offering workflow when it comes to adding enrollment experiences to different web pages, as the wizard UI can create the forms and embed it directly into the intended page. No more need to separately create the form, find the intended page, and then embed it into the form. The wizard UI takes care of it for you by launching directly from the embed form component on the page. And before I pass it on, we have one more feature to highlight focused around enhancing adaptive forms. This feature centers around automatically detecting hidden fields and excluding them from any documents of record that are created. In the past, the list of hidden form fields were passed to the server for processing via metadata tags and submitted data. This would exclude the hidden fields from documents of record so that these documents of record would be created with the intended fields hidden. However, LOB apps could not determine the hidden fields as they didn’t understand the metadata tags, which are internal forms data structure. Therefore, documents of record were created that were not accurate as the intended hidden fields weren’t actually hidden. Now form authors can specify at the form level to exclude hidden fields from documents of record and enable server-side validation to automatically generate optimized and relevant documents of record with the hidden fields actually excluded. This leads to the creation of correct documents of record, maintaining the integrity of the intended documents of record. This month for experience manager sites, we launched the ability to view language copies of content fragments within the content fragment admin console. As suggested, this feature allows users to see if a content fragment has language copies and the number of language copies associated with it. Additionally, users can also view content fragments created in a specific locale. Users can do so by choosing to display the language column in the content fragment admin console. This column will display the locale in which a content fragment is created and will also display the number of language copies associated with it. This number is a clickable button which will display a dialog showing all of these language copies and their status. This is a quick way to access this information and even if a user wants to filter by a specific locale, they can do so via the filter panel by selecting the locale from the filter option available in the UI. I’ll now pass it along to Cloud Service Foundation. Last, we have a Cloud Manager update for Cloud Service Foundation. In keeping our commitment to maintain and update Cloud Manager on AM as a cloud service, we have released this month an improved resiliency and reduced errors. To improve resiliency of the new user experience, infrequent cases of repository patient failures and Visual Studio team system org setup errors have been reduced and improved New Relic user creation validation prevents errors. We’ve updated the AM project archetype to ensure new projects created from Cloud Manager apply the latest AM best practices. The AM project archetype is a Maven template that creates a minimal best practices based project as a starting point for AM websites. The AM project archetype 37 includes multiple enhancements and new features. As a reminder, the list of features in our last announcement that were under pre-release are now available in production. For more detailed information, please go to the release notes listed here. Thank you for joining us.