Adobe Experience Manager Forms as a Cloud Service brings some notable changes to existing features in comparison to Adobe Experience Manager Forms On-Premise and Adobe-Managed Service environments. The key differences are listed below:
The service has a Cloud-native architecture that allows auto-scaling based on load, Zero downtime for upgrades, frequent and after roll-out of new features and updates, and topologies optimized for maximum resilience and efficiency.
The service includes no submit actions that stores data to Adobe Experience Manager Cloud Service instances, making it super secure. Data captured via forms is sent directly to configured data stores.
A free CDN (content delivery network) is also included to help you deliver and render forms at a faster pace.
The service provides an SDK to develop and test custom code in a local environment (local machine) before deploying the code to a Cloud Service. Developers develop and test custom components, themes, workflows applications, configurations, templates, and more using the SDK on their local machines. After testing the custom code in their local development environment, they deploy the custom code to a Forms CS environment development or stage environment for further testing before promoting it to a production environment.
Developers maintain code for Cloud Service and local development environment in a common git repository. A git repository, based on AEM Archetype, is auto created on creation of an AEM as a Cloud Service program.
Development flow for Forms as a Cloud Service aligns with AEM Archetype for AEM Cloud Service. 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.
Before using your customer bundles with Forms as a Cloud Service, recompile your custom code with the latest version of adobe-aemfd-docmanager.
Use AEM Forms as a Cloud Service migration utility to prepare and migrate your Adaptive Forms, themes, templates, and cloud configurations from AEM 6.4 Forms on OSGi and AEM 6.5 Forms on OSGi to AEM as a Cloud Service. Use Git repository of your program to import existing Adaptive Form templates.
Email supports 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.
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 a 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
Adobe recommends using Dispatcher or CDN caching. It helps improve rendering speed of prefilled forms.
Rule editor: AEM Forms as a Cloud Service provides a hardened Rule editor. The code editor is not available on Forms as a Cloud Service.
The migration utility helps you migrate your forms that have custom rules (created in code editor). The utility converts such rules into custom functions supported on Forms as a Cloud Service. You can use the reusable functions with Rule editor to continue obtaining results obtained with rule scripts. The
onSubmitSuccess functions are now available as actions in the Rule Editor.
Prefill Service: By default, the prefill service merges data with an Adaptive Form at client as opposed to merging data on Server in AEM 6.5 Forms. The feature helps improve the time required to prefill an Adaptive Form. You can always configure to run the merge action on the Adobe Experience Manager Forms Server.
Submit actions: The Email submit action provide options to send attachments and attach Document of Record (DoR) with email. You can use it inplace of the Email as PDF action available in AEM 6.5 Forms.
Automated Forms Conversion Service: The service does not provide meta-model for Automated Forms Conversion Service. You can download it from Automated Forms Conversion Service documentation.
XSD-Based Adaptive Forms: You can use XDP-template to design a template for Document for Record. The service does not support XFA based Adaptive Forms
Components: You can use Adaptive Forms Core-Components to design your forms. These components are based on WCM Core Components, follow BEM standards, and can be easily customized. The service does not support in-form signing experience and does not include the Summary and Verify components for Adaptive Form
You can use the Search & Lister, Drafts and Submission, and Link components of Forms Portal to list forms for logged-in users. Support for anonymous use of Forms Portal is not available out of the box (OOTB). You can customize the Forms Portal to enable displaying forms for non-logged in users.
The service does not retain metadata for drafts and submitted Adaptive Forms.
Forms as a Cloud Service provide Document Generation and Document Manipulation RESTful APIs. You can use these APIs to generate or manipulate docs on demand or in batches, as required:
Document Services: Document Generation APIs (Output Service): In a single API call or batch, you can use only one template with multiple DATA XML files. Using multiple templates with multiple data files in a single API call is not supported.
Document Manipulation APIs (Assembler Service):
The operations that rely on document services or applications are not available. For example, Microsoft Word to PDF, Microsoft Excel to PDF, and HTML to PDF, PostScript (PS) to PDF, XDP to PDF Forms are not supported. These operations rely on Microsoft Office, Adobe Acrobat, Adobe Distiller, Forms Document Service respectively.
Convert documents that are in a non-PDF format into a PDF format before using those with Communications Document Manipulation APIs. For example, if your documents are in Microsoft Office, HTML, PostScript (PS), XDP format, convert these documents to PDF format before using those with PDF documents. You can use the ConvertPDF service for such conversions.
You can use an AEM 6.5 Forms environment for Digital Signature, Encryption, Reader Extension, Send to printer, Convert PDF, and Barcoded Forms service.
The service also provides support for JDBC connector, Microsoft Dynamics, SalesForce, SOAP-based web services, and services that support OData.
You can also connect AEM user profile to retrieve and update user information.
Forms data model supports only HTTP and HTTPS endpoints to submit data. The service does not support Mutual SSL for REST connector and x509 certificate-based authentication for SOAP data sources.
Forms as a Cloud Service allows to use Microsoft Azure Blob, Microsoft Sharepoint, Microsoft OneDrive, and services supporting general CRUD (Create, Read, Update, and Delete) operations as data stores, both Open API specification 2.0 and Open API 3.0 specification are supported.
The service provides an OOTB integration with Adobe Sign and supports DocuSign for e-signatures.
The service also supports Adobe Sign roles. You can configure the roles in Adaptive Forms editor for business users to easily configure signing workflows.
You can use an AEM 6.5 Forms environment to:
render your XDP-based forms as HTML5 Forms. The service does not support HTML5 Forms (Mobile Forms).
capture data offline and sync it the next time you return online with AEM Forms Workspace app.