Adobe Experience Manager Forms supports JSON Schema as a form model for creating Adaptive Forms with structured data bindings.
However, the uploaded schema must satisfy AEM Forms' resource identification requirements. Adobe explicitly specifies that JSON Schema filenames must end with the .schema.json extension. For example, a schema named employee.json should be named employee.schema.json before being uploaded for use as an Adaptive Form model.
This naming convention enables AEM Forms to recognize the file as a JSON Schema resource when the developer searches for available schemas during form creation.
The developer can select the Schema form-model option and choose an existing schema from the repository or upload a schema directly from the local file system.
Option B is not supported by the scenario because the problem described is schema discovery, not a reported validation failure. Nevertheless, syntactically valid JSON must also conform to the JSON Schema structure expected by the form model.
Option C is not inherently a configuration error because the Forms and Documents repository is used to manage form-related assets. Option D is incorrect because a schema does not universally require a default property.
Official Adobe references:
Creating Adaptive Forms Using JSON Schema — Required .schema.json Filename Convention
Submit