Protected Mode
AEM Forms server lets you run JavaScript code. A malicious JavaScript code can harm an AEM Forms environment. Protected mode restricts AEM Forms to run XDP files only from trusted assets and locations. All the XDP available in AEM Forms UI are considered trusted assets.
The protected mode is on, by default. If necessary, you can disable the protected mode:
- Log in to AEM Web Console as an administrator. The URL is https://‘[server]:[port]’/system/console/configMgr
- Open Mobile Forms Configurations for editing.
- Deselect the Protected Mode option and click Save. The protected mode is disabled.
Updating referenced XFA forms
In AEM Forms, an XFA form template can be referred by an adaptive form or another XFA form template. Also, a template can refer to a resource or another XFA template.
An adaptive form referring to an XFA have its fields bound with the fields available in the XFA. On updating a form template, the associated adaptive form attempts to synchronize with the XFA. For more details, see Synchronizing adaptive forms with the associated XFA.
Removing a form template corrupts the dependent adaptive form or form template. Such an adaptive form is sometimes informally referred to as a dirty form. In AEM Forms user interface, you can find the dirty forms in the following two ways.
- A warning icon is displayed on the adaptive form thumbnail in asset listing and the following message is displayed when you hover the pointer over the warning icon.
Schema/Form Template for this adaptive form has been updated so go to Authoring mode and rebase it with new version.
A flag is maintained to indicate if an adaptive form is dirty. This information is available on the form properties page, alongside the form metadata. Only for dirty adaptive forms, a metadata property Model Refresh
displays Recommended
value.