AEM Forms as a Cloud Service

 AEM Forms as a Cloud Service

1. The Code Editor is not available on Forms as a Cloud Service. If your Adaptive Form uses rule scripts developed using code editor, use the Migration Utility to convert your code scripts to custom functions. You can use custom functions with Visual Editor to continue obtaining the results obtained with Code Editor.

2. You can create an XFA-based Adaptive Form on Cloud Service instance. However, support for XFA-based Adaptive Forms is not available for AEM Forms as a Cloud Service SDK (Local development environment).

3. You can migrate your custom code, content, and assets from On-Premise or Adobe-Managed Services environments to Forms as a Cloud Service environment.

4. You can continue using themes created with AEM 6.4 Forms and AEM 6.5 Forms after you use the Migration Utility to move them to AEM Forms as a Cloud Service.

5. You can connect a Form Data Model to RESTful web services, SOAP-based web services, OData services, and Experience Manager user profile as data sources. Support to connect a Form Data Model with a relational database is not available.

6. You can modify your existing Adaptive Forms to use Submit to REST endpoint, Send email, Submit using Form Data Model, and Invoke an AEM Workflow Submit actions. Forms Portal and Forms Portal submit action are not available yet. Keep an eye on monthly release notes for the availability of the features.

7. Create the Adaptive Form based on the JSON schema on Experience Manager 6.5 Forms environment and use the Migration utility to migrate such Adaptive Forms to AEM Forms as a Cloud Service. The utility converts such events into client libraries and you can continue using Adaptive Forms with events in a Cloud Service environment.

8. The Verify step is not available for Forms as a Cloud Service. Remove the verify step from your existing Adaptive Forms before moving such forms to a Cloud Service environment.

9. The Signature step is not available for Forms as a Cloud Service. Remove the Signature step in your Adaptive Forms. Instead of Signature step, allow the users to Sign an Adaptive Form after submission. It helps you continue providing an in-browser signing experience.

10. You can continue using themes created with AEM 6.4 Forms and AEM 6.5 Forms after you use the Migration Utility to move them to AEM Forms as a Cloud Service.

You can also create a project based on AEM Forms as a Cloud Service Archetype and use included sample themes and templates.