AEM Forms Developer Expert key terms

A dynamic HTML form built on a form model that renders differently per device and can show, hide, or require fields based on user input and rules.

A schema-like layer that connects an Adaptive Form to backend data sources such as REST services, SOAP services, or databases, exposing data and services as reusable objects.

A configured connection to an external system (REST endpoint, SOAP service, database, or OData) that supplies the schema and operations used by a form data model.

The visual authoring tool where developers define client-side logic such as show/hide, set value, validate, and invoke service without writing JavaScript directly.

A packaged bundle of CSS and JavaScript stored in the repository under a category name, which templates and components reference to load styling and behavior.

A container component that groups child fields and can repeat, be nested, or be toggled, making it the usual target for layout and visibility rules.

A reusable portion of an Adaptive Form, such as a panel or field group, that can be embedded in multiple forms and updated once for all consumers.

A styling layer applied to an Adaptive Form that controls typography, colors, spacing, and component appearance without editing individual field properties.

A developer-built form component created by extending a base component and registering it so authors can drag it onto forms.

An annotation-driven Java class bound to a resource type that exposes server-side data and logic to HTL templates and components.

A server-side templating language that keeps markup clean by restricting expressions to a safe subset and escaping output automatically.

The schema definition a form is bound to, such as an XML schema, JSON schema, or form data model, which determines available fields and submission format.

The mapping that links a form field to a node or property in the underlying model so values are read on load and written on submit.

The process of populating form fields with existing data at load time, often from a data source or submitted record, so users do not re-enter known values.

A service operation exposed by a form data model, such as a read or write call, that rules or workflow steps can invoke at runtime.

A configured step that transforms or enriches data before it reaches a form data model service, such as adding headers or reshaping a payload.

The handler that determines what happens when a form is submitted, such as sending data to a REST endpoint, starting a workflow, or generating a document.

A client-side JavaScript API that lets custom scripts interact with an Adaptive Form, including reading fields, triggering events, and controlling submission.

A JavaScript function registered with the rule editor so authors can call organization-specific logic from visual rules instead of inline scripts.

A legacy XML-based form format with its own layout and scripting model that can be rendered or converted in the platform.

An XML Data Package file that stores an XFA form design plus related resources, commonly used as a template for document rendering.

A document service that merges a template with data to produce final output such as PDF, allowing batch generation and print-ready rendering.

A design file, such as an XDP or form design, used by output generation to define layout and placeholders for merged data.

A document service that combines, reorders, or splits PDFs and other documents into a single assembled output.

An automated process, often built in the workflow engine, that routes a submitted form through review, approval, or data tasks.

A workflow step that creates a to-do for a user or group, presenting a form or document for review and capturing their decision.

Repository-level rules granting or denying read, write, or delete permissions on content paths to users and groups.

A collection of users that shares permissions and workflow assignments, simplifying administration of access across many accounts.

Policies applied to generated PDFs that restrict printing, copying, or editing and can require credentials to open the file.

A caching and security layer placed in front of the application server that serves static assets and filters incoming requests.

The process of packaging code and content into packages and installing them on target environments, often automated through pipelines.

The tool used to build, upload, and install content packages that carry forms, components, and configuration between environments.

The two-tier topology where authors edit content on an author instance and visitors receive published content from publish instances.

The mechanism that maps an incoming URL to a resource and then selects the script or servlet that renders it based on resource type.

A modular Java archive deployed to the runtime that can register services and be configured without restarting the whole system.

A machine-readable API description format used to import REST service definitions into a data source so operations become available to forms.

Adjusting caching, thread pools, form complexity, and data call patterns to reduce load times and prevent timeouts under traffic.

Reviewing server and error logs to trace failures such as rendering errors, failed service calls, or permission denials during troubleshooting.