Storing and handling form data is one of the most important aspects to consider while designing forms.
In a production environment, it is recommended not to store submitted form data in the AEM repository. The default implementation of Forms Portal Store, Store Content, and Store PDF submit actions store form data in the AEM repository. These submit actions are meant only for demonstration purposes. Also, the Save and Resume and Auto Save features use portal storage by default. Therefore, consider the following recommendations:
Storing draft data: If you are using the Draft feature of adaptive forms, you should implement a custom Service Provider Interface (SPI) to store draft data in more secure storage like a database. For more information, see Sample for integrating drafts & submissions component with database.
Storing submission data: If you are using Form Portal Submit Store, you should implement a custom SPI to store submission data in a database. See Sample for integrating drafts & submissions component with database for a sample integration.
You can also write a custom submit action that stores form data and attachment in secure storage. See Writing custom Submit action for adaptive forms for more information.
Length of draft ID: When you save an adaptive form as a draft, a draft ID gets generated to uniquely identify the draft. The minimum value for the length of the draft ID field is 26 characters. Adobe recommends setting the draft ID length to 26 or more characters.
Handling personally identifiable information
One of the key challenges for organizations is how to handle personally identifiable (PII) data. Some best practices that will help you handle such data are as follows:
refer:
https://experienceleague.adobe.com/docs/experience-manager-65/forms/adaptive-forms-basic-authoring/a...
