Configuring storage services for drafts and submissions

Last update: May 24, 2024

CREATED FOR:

  • Admin
  • User
  • Developer

Overview

With AEM Forms, you can store:

  • Drafts: A work-in-progress form that end users fill and save for later, and submit afterwards.

  • Submissions: Submitted forms containing user provided data.

AEM Forms Portal data and metadata services provide support for drafts and submissions. By default the data is stored in the publish instance, which is then reverse-replicated to configured author instance to be available for percolation to other publish instances.

The concern with the existing out-of-the-box approach is, that it stores all the data on publish instance, including the data which can be Personal Identifiable Information (PII).

In addition to above mentioned default approach, an alternative implementation is also available for directly pushing the form data to processing instead of saving it locally. Customers having concerns about storage of potentially sensitive data on publish instance can choose the alternative implementation in which the data is sent to a processing server. Since processing happens on the author instance, it typically stays in a secure zone.

NOTE
When you use the Forms Portal submit action or enable the Store data in forms portal option in adaptive form, the form data is stored in AEM repository. In a production environment, it is recommended not to store draft or submitted form data in AEM repository. Instead, you must integrate the drafts and submission component with a secure storage like enterprise database to store drafts and submitted forms data.

Configuring Forms Portal drafts and submissions services

In the AEM Web Console Configuration ( https://[host]:'port'/system/console/configMgr), click to open Forms Portal Draft and Submission Configuration in edit mode.

Specify the values for properties based on your requirements as described below:

Out of the box services to store data on publish instance

Data is reverse replicated to configured author instance.

PropertyValue
Forms Portal Draft Data Service(Identifier for draft data service (draft.data.service))com.adobe.fd.fp.service.impl.DraftDataServiceImpl
Forms Portal Draft Metadata Service (Identifier for draft metadata service (draft.metadata.service))com.adobe.fd.fp.service.impl.DraftMetadataServiceImpl
Forms Portal Submit Data Service (Identifier for submit data service (submit.data.service))com.adobe.fd.fp.service.impl.SubmitDataServiceImpl
Forms Portal Submit Metadata Service (Identifier for submit metadata service (submit.metadata.service))com.adobe.fd.fp.service.impl.SubmitMetadataServiceImpl

Out of the box services to store data on remote processing instance

Data is pushed directly to configured remote instance

PropertyValue
Forms Portal Draft Data Service(Identifier for draft data service (draft.data.service))com.adobe.fd.fp.service.impl.DraftDataServiceRemoteImpl
Forms Portal Draft Metadata Service (Identifier for draft metadata service (draft.metadata.service))com.adobe.fd.fp.service.impl.DraftMetadataServiceRemoteImpl
Forms Portal Submit Data Service (Identifier for submit data service (submit.data.service))com.adobe.fd.fp.service.impl.SubmitDataServiceRemoteImpl
Forms Portal Submit Metadata Service (Identifier for submit metadata service (submit.metadata.service))com.adobe.fd.fp.service.impl.SubmitMetadataServiceRemoteImpl

Apart from the configuration specified above, provide information about the configured remote processing instance.

In the AEM Web Console Configuration ( https://[host]:'port'/system/console/configMgr), click to open AEM DS Settings Service in edit mode. In the AEM DS Settings Service dialog, provide information about processing server URL, processing server user name, and password.

NOTE
A sample implementation is also provided for storing user data in a database. To understand how to configure data and metadata services to store user data in an external database, see Sample for integrating drafts & submissions component with database.

Experience Manager


Espressos & Experience Manager: AEM Forms

Espressos & Experience Manager

Thursday, Mar 6, 7:00 PM UTC

Join Adobe's AEM product team as they highlight AEM Forms' latest innovations, including: the new Gen AI Assistant, Unified Composition with AEM Sites, and new ways to deploy forms through conversations.

Register

Connect with Experience League at Summit!

Get front-row access to top sessions, hands-on activities, and networking—wherever you are!

Learn more

Register now