AEM Forms Backend Developer Professional key terms

A responsive HTML form authored in AEM Forms that renders differently across devices and can be submitted to a server or processed client-side. It is built from components, panels, and a data model rather than a fixed PDF layout.

A schema-like layer that connects an adaptive form or document to backend data sources such as REST services, SOAP services, OData, or relational databases. It exposes read and write operations that forms and workflows can invoke without custom code.

A configured connection to an external system (REST endpoint, SOAP service, OData provider, or JDBC database) that an FDM uses to read or write data. Each data source is defined once and can be reused by multiple form data models.

The mapping that ties a form field to a node or property in the form's data model, so user input is stored in and read from that location. Changing the binding changes where the value lives in the submitted payload.

The XML instance document that holds the current values of an adaptive form when bound to an XML schema or FDM. It is what gets submitted, prefilled, and validated against the schema.

A definition of the structure, element types, and constraints of an XML document. Adaptive forms can be based on an XSD so fields are generated from schema elements and submissions are validated against it.

A visual authoring tool in adaptive forms for defining conditional logic, calculations, validation, and service invocations without writing JavaScript. Rules are evaluated on the client and can call FDM operations.

A reusable portion of an adaptive form (such as an address block or consent panel) that can be inserted into multiple forms and updated in one place. Fragments reduce duplication and keep forms consistent.

A set of styling rules (CSS, LESS, fonts, and layout options) applied to an adaptive form to control its appearance. Themes separate presentation from form structure so one form can be restyled without editing components.

A reusable definition that supplies page structure, header and footer, and default styling for adaptive forms. Authors select a template when creating a form, and template changes can propagate to forms built on it.

The configured behavior that runs when a user submits an adaptive form, such as submitting to a REST endpoint, emailing, invoking a Forms Workflow, or generating a PDF via a Document Services action.

The endpoint that receives an adaptive form's submitted data when the submit action is set to post to a URL. It must accept the payload format (XML, JSON, or form-encoded) that the form produces.

A JEE workflow (built on the AEM Forms Workflow engine) that routes a submitted form or task through human steps and automated process steps. It is used for review, approval, and document generation pipelines.

A workflow step that executes a component or service automatically rather than waiting for a person. Examples include invoking a Document Services operation, running a custom OSGi service, or calling an FDM operation.

The configuration that determines which user or group receives a human workflow step and what form they see. It can assign to a specific user, a group, or a dynamically resolved principal.

The end-user web application where assignees view their task list, open assigned forms, and complete or route tasks. It surfaces Forms Workflow tasks and tracks their status.

A Document Services component that merges a form design (XDP) with XML data to produce a PDF or other rendered output. It supports print, interactive PDF, and various output formats and locales.

A Document Services component that combines, splits, overlays, and manipulates PDFs and other documents using a Document Description XML (DDX) instruction file. It is the standard way to assemble output packages.

Document Description XML: an instruction document that tells the Assembler Service which input documents to use and what operations (merge, watermark, split, convert) to perform, and where to place results.

XML Data Package: the file format produced by Designer that contains a form design, its data, and related resources. Output Service and Forms use XDP as the template input for rendering PDFs.

The visual layout and field structure of a form created in AEM Forms Designer and saved as an XDP. It defines static and interactive elements that Output Service or rendered forms use.

Parameters passed to Output Service that control output format, locale, tagged PDF, linearization, and whether the result is interactive or print-only. Choosing the right options affects accessibility and file size.

A PDF that carries structural tags identifying headings, lists, tables, and reading order so assistive technology can interpret it. Output Service can produce tagged output when the option is enabled.

An ISO-standardized PDF profile for long-term archiving that restricts features (such as external fonts or encryption) to guarantee faithful future rendering. Document Services can generate PDF/A-compliant output.

The AEM Forms capability for authoring personalized customer letters from reusable text, data elements, conditions, and layouts, then generating them on demand. It separates content authoring from the data that personalizes each letter.

The AEM Forms capability for producing personalized, interactive web and print communications (such as statements or notices) that adapt to recipient data and channel. It extends correspondence concepts to responsive web output.

A schema of the data elements used in correspondence or interactive communications, defining names, types, and structure. It lets authors insert data placeholders that are filled at generation time.

A Correspondence Management artifact composed of reusable content modules, data elements, conditions, and a layout. It is the unit that gets rendered into a personalized document for a recipient.

The output path in Interactive Communications that renders a communication as a print-ready PDF, often via an XDP layout. It differs from the web channel, which renders responsive HTML.

The output path in Interactive Communications that renders a communication as responsive HTML for browser viewing. It supports interactive elements and device-specific layout.

The collection of AEM Forms services that generate and manipulate documents, including Output, Assembler, Forms, Convert PDF, and PDF Utilities. They are typically invoked via APIs, workflows, or OSGi services.

A Java component registered in the OSGi container that other components can discover and invoke through service interfaces. Custom AEM Forms logic is often packaged as an OSGi service consumed by workflows or servlets.

A Java HTTP endpoint registered against a resource type or path that handles requests in AEM. Custom form submission handlers, prefill endpoints, and integrations are frequently implemented as Sling servlets.

A Java class implementing the workflow process interface that executes a step in a Forms Workflow. It receives workflow metadata and can call Document Services, FDMs, or external systems.

The client-side API that lets an HTML5-rendered form communicate with the surrounding page, enabling prefill, submit, and field value access. It is used when embedding rendered forms in custom pages.

The programmatic interface (Java or web service) used to invoke Output, Assembler, and related services. It accepts input documents and options and returns generated documents or status objects.

A set of AEM components and services that let end users discover, open, and track forms and submissions. It provides draft, submission, and search capabilities on top of stored form data.

The configured persistence (such as a database or CRX node store) where saved drafts and submitted form data are kept. Correct configuration is required for users to resume drafts or for portals to list submissions.

The set of permissions (read, write, replicate, etc.) granted to users or groups on a repository path. Forms assets and submission data are protected by ACLs evaluated at request time.

A predefined AEM group (such as forms-users or forms-power-users) that bundles the permissions needed to use or administer Forms features. Assigning users to the correct group is the standard way to grant Forms access.

Any identity (user or group) that can be granted permissions in AEM. Access control decisions compare the requesting principal against the ACLs on the target resource.

A single sign-on mechanism where an identity provider authenticates the user and asserts identity to AEM. It is commonly configured so form authors and users log in once across Forms applications.

The AEM caching and security layer placed in front of the publish tier that filters requests and caches responses. Forms deployments must configure it to allow required endpoints while blocking sensitive ones.

The practice of adjusting JVM heap, thread pools, document service timeouts, database connection pools, and cache settings to meet throughput and latency targets for forms and document generation.

Diagnosing Forms problems by reading error logs, service health checks, thread dumps, and Document Services status pages, then correlating failures to configuration, permissions, or resource limits.

The Java EE deployment model of AEM Forms that provides Document Services, Forms Workflow, and related server components. It is distinct from the OSGi-based authoring tier and requires its own installation and administration.