Adobe Experience Manager Forms as a Cloud Service brings some notable changes to existing features in comparison to Adobe Experience Manager FormsOn-Premise and Adobe-Managed Service environments. The key differences are listed below:
The service provides a local and a cloud-native development environment. You can use a local development environment to develop and test your custom code, components, templates, themes, Adaptive Forms, other assets before deploying these assets to a cloud environment. It helps speed up the development process.
AEM as Cloud Service is shipped with a built-in CDN. Its main purpose is to reduce latency by delivering cacheable content from the CDN nodes at the edge, near the browser. It is fully managed and configured for optimal performance of AEM applications.
A cloud-native environment does not have web console (configuration manager). You can use AEM Forms as a Cloud Service SDK to generate configurations and CI/CD pipeline to deploy the configuration to your Cloud Service instance.
URL convention of localized Adaptive Forms now supports specifying a locale in the URL. New URL convention enables caching localized forms on a Dispatcher or CDN. On Cloud Service environment, use the URL format
http://host:port/content/forms/af/<afName>.<locale>.html to request a localized version of an Adaptive Form instead of
http://host:port/content/forms/af/afName.html?afAcceptLang=<locale>. Adobe recommends using Dispatcher or CDN caching. It helps improve rendering speed of prefilled forms.
Prefill service merges data with an Adaptive Form on a client. It helps improve the time required to prefill an Adaptive Form. You can always configure to run the merge action on the Adobe Experience Manager FormsServer.
Email support only HTTP and HTTPs protocols, by default. Contact the support team to enable ports for sending emails and to enable SMTP protocol for your environment.
Adobe Experience Manager Forms as a Cloud Service brings many new features and possibilities into your AEM Projects. However, there are some changes required to Adobe Experience Manager Maven projects to be compatible with AEM Cloud Service. At a high-level, AEM requires a separation of content and code into discrete subpackages to respect the split between mutable and immutable content. Use the Repository Modernizer tool to restructure existing project packages by separating content and code into discrete packages to be compatible with the project structure defined for Adobe Experience Manager as a Cloud Service.
For a comprehensive list of changes in Adobe Experience Manager as a Cloud Service, See What is New and What is Different.
The following features and enhancements are available only on AEM Forms as a Cloud Service:
Enhanced Visual Rule editor
The service provides a hardened Visual Rule editor. The service has added following features to Visual rule editor to help you write capable rules:
New submission events:
Successful Submission, and
New data type
scope. You can use the
scope data type in a custom function to pass the entire scope of a form.
Ability to use @this to specify a JSDoc in a custom function. It allows invoking a custom function by using @this in an active component.
Ability to add conditions for property-based rules.
The Core Components are a set of standardized Web Content Management (WCM) components for AEM to speed up development time and reduce maintenance cost. AEM Forms as a Cloud Service supports AEM Forms Container Core Component. You can use the component to embed an Adaptive Form to an AEM Sites page.
AEM Archetype for Forms as a Cloud Service
AEM Archetype helps you start developing for AEM Forms as a Cloud Service. You can use Archetype version 27 or later to create a project template compatible with AEM Forms as a Cloud Service environment. The Archetype also includes some sample themes and templates to help you started quickly.
Secure and improved information flow between forms and Sign
Adaptive Forms and Adobe Sign integration on Cloud Service offer simultaneous submission of data and signing activity. It makes form submission independent of signing status paving a way for faster submissions. On top of it, the service does not save any data on Cloud Service instances making the signing process super secure.
Best Practices Analyzer and migration tooling
Best Practices Analyzer provides an assessment of your current AEM implementation. Run the tool before migrating to Forms as a Cloud Service. It assesses readiness to move from an existing Adobe Experience Manager (AEM) deployment to AEM as a Cloud Service.
The service also provides an improved migration experience to help you easily migrate from AEM 6.4 Forms and AEM 6.5 Forms to AEM Forms as a Cloud Service.
Faster form renditions and Faster server-side validations
The service uses CDN and Dispatcher caching to deliver faster renditions and server-side validations for Adaptive Forms.
You can now validate CAPTCHA either on Adaptive Form submission or on a business logic. You can also add conditions to validate CAPTCHA on a user action and show or hide the CAPTCHA component in an Adaptive Form based on rules.
The CAPTCHA component provides an out-of-the-box integration with Google reCAPTCHA. You can also configure more CAPTCHA services for the component, if necessary.
Multiple master pages for Document of Record
You can now use a different master page for each page of a Document of Record and control placement of an Adaptive Form panel on a Document of Record with pagination options.
Add columns to headless tables
You can add and delete columns to tables without headers. Hidden headers are added to such tables to help you add and delete columns. These headers are visible during authoring but remain hidden in the published form. Tables without headers are mostly found in Adaptive Forms created using the Automated Forms Conversion Service.
Improved Submit Actions
You can use the Send Email Submit Action to send a Document of Record (DoR) PDF as an attachment.
Group email for workflow
You can choose to send notification emails from the Assign Task step to a single person or a group.
Enhanced Invoke Form Data Model step
You can now specify path of folder for the Relative to Payload option of input service arguments in an Invoke Form Data Model step. It helps you map a file present in the specified folder to the service argument without specifying the exact filename.
Improved readability of translation files
On Forms as a Cloud Service, reading order of the fields and panels of an Adaptive Form and message keys of corresponding translation files (.XLIFF files) has similar structure. It helps improving manual translation speeds.