In AEM Forms app that syncs with an AEM Forms instance on OSGi, only field level attachments are supported for adaptive forms. Perform the following steps to prevent users on iOS devices from experiencing data loss:
- In your server, navigate to: Adobe Experience Manager > Tools > Operations > Web Console.
- Find and click Adaptive Form Configuration Service.
- In the Adaptive Form Configuration Service dialog, enable Make File Names Unique.
Ensure that Make File Names Unique setting is enabled. If Make File Names Unique setting is disabled, users experience data loss if they try to submit adaptive forms with multiple attachments.
For mobile forms enabled in AEM Forms app, with HTML Render Profile as Save as Draft Profile, saved drafts are not visible to workspace users. To let workspace users see the saved drafts of mobile forms submitted by them on the portal:
- Open CRXDE and login with administrator credentials.
- In the root path of the CRXDE, in the Access Control List under Access Control, click +.
- In the Add New Entry dialog, click the group search button in the Principal field.
- In the Name field of the Select Principal dialog, type PERM_WORKSPACE_USER and click Search.
- Select PERM_WORKSPACE_USER group in the Select Principal dialog, click OK.
- In the Add New Entry dialog, PERM_WORKSPACE_USER group is selected in the Principal field.
Enable jcr:read privileges for the user group.
- Click OK.
Troubleshooting: Mobile forms that are not cached fail in AEM Forms app if the AEM Forms app is connected to an older AEM Forms server
Perform the following steps if the mobile form fails in AEM Forms app when it is connected to an older AEM Forms server:
Troubleshooting: Form does not sync on windows if path of the form or any of its resources is more than 256 characters
In the AEM Forms App on Windows, a form does not sync if path of the form or any of its resources is 256 characters or more. To fix this, modify the path of the form and its resources to reduce the number of characters in the path.
For AEM Forms to work with AEM Mobile apps, ensure that:
- aemfd.angular.mobile.core is present.
- Form is published to the publish server.
If a user encounters a problem in opening a form in AEM Mobile, ensure that the form is published to the publish server.
The AEM Form component logic is handled by the angular module: cqFormModule. If you have not changed the top-level module name, a dependency on cqFormModule is automatically injected on the inclusion of aemfd.mobile.angular.core.
If you have changed the top-level module name, ensure that you add a dependency of the module cqFormModule to the top-level module.
By default, when you create a mobile app using AEM Mobile, the top level module is called AEMAngularApp module. See, AngularJS Application Module.