AEM Forms Backend Developer Professional flashcards

32 cards. Read the term and the definition here. The deck at the top of this page is optional.

AEM Forms on OSGi

Deployment model where the Forms add-on package installs Forms services as OSGi bundles on the AEM/JCR stack, with no separate application server or Forms database.

AEM Forms on JEE

Deployment model where Forms services run on a separate Java EE application server (e.g., JBoss, WebLogic) with their own database, exposing services as web services.

PDF Generator native binaries

Platform-specific conversion libraries required by the PDF Generator service to convert Office, PostScript, and image files to PDF; they must match the Forms add-on version.

bindRef

Adaptive Form field property that maps the field to a data model node; an empty bindRef means the field's value is not included in submitted data.

guideBridge

Client-side JavaScript API for interacting with an Adaptive Form, providing methods such as getFormData, setData, validate, and event subscription.

Form Data Model

A data integration asset backed by JDBC, REST, SOAP, or OData sources that generates get, read, and write services consumed by Adaptive Forms, IC, and workflows.

DDX

XML document used by the Assembler service that describes input documents and the desired output operation, such as assemble, convert, transform, or extract.

Output service

Document Service that renders an XDP template plus XML data into PDF or other formats, with options for PDF/A, tagged PDF, and font embedding.

Reader Extensions

Document Service that applies usage rights, such as save or comment, to a PDF so the rights are honored by Adobe Reader.

Assign Task step

Forms Workflow step that creates a task in the AEM Inbox, referencing the task form by path and storing payload data in workflow metadata.

WorkflowProcess interface

OSGi interface implemented by custom workflow steps, with an execute method receiving WorkItem, WorkflowSession, and MetaDataMap parameters.

MetaDataMap

Workflow data container passed to process steps that carries payload and metadata, including arguments passed via the workflow args map.

Data Dictionary

Correspondence Management asset defining data elements and their types, mapping to the XML schema used for letter and IC personalization.

Interactive Communications

Multi-channel correspondence capability extending letters to print, web, and mobile channels using document fragments, charts, and a data model.

Text fragment

Reusable text block in Correspondence Management that can contain variables and is assembled into letters or Interactive Communications.

Layout fragment

Correspondence Management asset defining the visual structure of a letter, including target areas where content fragments are placed.

AEM ACLs for Forms

Access control entries on forms, Form Data Models, and letters; users need read permission on the form and all referenced assets to render it.

CSRF filter

AEM security filter requiring a CSRF token for state-changing requests, including Forms REST endpoints that submit or modify data.

Secure vault

AEM mechanism using CryptoSupport to encrypt stored credentials, used to avoid plaintext passwords in OSGi configurations and data source settings.

SubmitAction interface

OSGi interface implemented by custom Adaptive Form submit actions, registered as an OSGi service and referenced by name in the form's submit configuration.

PrefillDataProvider

Interface implemented by custom prefill services that populate Adaptive Form fields at render time; registered as an OSGi service and referenced by name.

DocumentServiceFactory

OSGi service used to obtain Document Services clients such as Output, Assembler, Forms, and Reader Extensions on the OSGi deployment.

Forms Document Services API

HTTP endpoint used on AEMaaCS to invoke Document Services, authenticated with service credentials, since local PDF Generator is unavailable on Cloud Service.

JDBC data source pool

OSGi configuration holding database URL, driver, and credentials that a Form Data Model references for relational data integration.

FDM associations

Relationships derived from foreign keys in a data source and exposed as navigation properties, used to bind nested or repeating panels in forms.

Workflow launcher

AEM configuration that triggers a workflow on node events, such as asset creation, or on form submission for Forms-centric workflows.

PDF/A output

Archival PDF variant produced by the Output service that requires embedded fonts and no encryption to remain compliant.

Dedicated PDF Generator instance

Deployment pattern placing PDF Generator on its own instance because conversion is CPU and memory intensive and competes with authoring workloads.

Sling health checks

AEM console page that reports service status, including Forms Document Service availability, used to validate a deployment.

Dispatcher Forms filters

Dispatcher rules that must permit paths such as /content/forms/af and /bin/forms so Forms Portal rendering and submissions reach AEM.

Workflow purge

Administrative operation that removes completed workflow instances to prevent repository bloat and maintain performance.

Forms add-on version match

Requirement that the Forms add-on package version equal the AEM quickstart and service pack version, otherwise bundles fail to resolve at startup.