AEM Forms Developer Expert flashcards
AEM Forms Developer Expert · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Forms add-on package
- An AEM package that installs the OSGi Forms capabilities (adaptive forms, document services, workflows). Its version must match the AEM service pack exactly or deployment fails.
- fd-service user
- The system user that owns AEM Forms Document Services operations, including PDF rendering and digital signing. It needs read access to form assets and the Trust Store credentials.
- PDF Generator service
- The Document Services component that converts Office, PostScript, and image files to PDF. It depends on native converter binaries installed on the host operating system, not inside AEM.
- bindRef
- The property on an adaptive form field that maps it to a node in the form's data model. An empty bindRef leaves the field unbound, so its value is not submitted.
- Panel fragment
- A reusable group of adaptive form components stored under /content/af/fragments. It can be inserted into multiple forms and must match the target form's data model.
- Wizard layout panel
- A panel type that splits its child panels into sequential tabs with next and back navigation. It is one of the responsive, accordion, and wizard panel layouts.
- guideBridge API
- The client-side JavaScript API for adaptive forms. Methods such as getFormData, validate, and resolveNode let scripts read data and manipulate field properties at runtime.
- Rule types
- The three rule categories in the adaptive forms rule editor: Format applies visual formatting, Validate enforces field validation, and Calculate computes a value from other fields.
- Custom component clientlib
- A client library that registers and styles a custom adaptive form component. Its JavaScript class extends a base component and is registered via the component node.
- Form Data Model
- A model built from a data source such as REST, SOAP, OData, or JDBC. It exposes get, insert, update, and delete services that forms can bind to and invoke.
- Pre-fill service
- An FDM get service invoked at render time to populate form fields with existing data. It runs before the form is displayed to the user.
- Repeatable panel binding
- A panel bound to a collection in the data model that repeats once per record. Each instance renders the fields for one collection entry.
- DDX file
- Document Description XML used by Assembler to define PDF operations such as combine, split, and watermark. It specifies inputs, outputs, and the operation to perform.
- Document of Record
- A read-only PDF generated from a submitted adaptive form using a DoR template. It captures the submitted data in a fixed, printable format.
- Reader Extensions
- A Document Services feature that adds usage rights to a PDF so Adobe Reader can save, sign, or comment. Rights are tied to a credential and policy.
- Participant step
- A workflow step that creates a task assigned to a user or group. The task appears in AEM Inbox and can be completed with submitted form data.
- Workflow payload
- The content path that a workflow instance operates on, stored under /var/workflow/instances. Process steps access it as workflowData in the metadata map.
- Dynamic participant chooser
- A service implementing ParticipantChooser that computes task assignees at runtime. It replaces static user or group assignment in participant steps.
- forms-users group
- The default AEM group for form authors. Members can create and edit adaptive forms, while forms-power-users can additionally publish and manage them.
- ACL on form assets
- Repository access control entries applied to paths such as /content/forms and /content/dam/formsanddocuments. They govern who can read, edit, and publish forms.
- CSRF token in submissions
- A security token included with adaptive form submissions to prevent cross-site request forgery. Custom submit endpoints must validate or explicitly exempt it.
- Dispatcher caching rule
- A configuration that caches static form assets but excludes dynamic form rendering and submit servlet paths. Caching POST responses would corrupt submissions.
- Forms log category
- The com.adobe.aem.forms logger that records adaptive form and Document Services activity. It is a primary source for diagnosing rendering and submission failures.
- Resolved bundle state
- An OSGi bundle state indicating dependencies are unmet, so the bundle is not active. In Forms deployments it usually signals a missing package or service dependency.
- Submission data store
- A configured location for storing adaptive form submissions, offloading them from the content repository. It prevents unchecked repository growth on busy forms.
- Adaptive form theme
- A client library that supplies CSS and styling for an adaptive form. It must be present on publish instances or the form renders unstyled.
- Submit to REST endpoint
- An adaptive form submit action that posts form data as JSON or XML to a configured URL. The endpoint must permit the form's origin.
- Assembler service
- A Document Services component that combines, splits, and manipulates PDFs according to a DDX file. It is commonly used in document assembly workflows.
- AEM Inbox
- The OSGi AEM interface where users see and complete assigned workflow tasks. It is the counterpart of the JEE Forms Workspace task UI.
- Trust Store credential
- A repository of certificates and private keys used for PDF signing and Reader Extensions. The fd-service user must own the signing key.
- Forms Manager
- The AEM UI for creating, publishing, and managing adaptive forms and related assets. It also triggers package deployment of form content.
- XFA to adaptive conversion
- A wizard that converts an XFA-based form into an adaptive form. The result uses the XFA schema as its data model and generated field bindings.