How to create a custom Time Bound Date of Birth Component and add in a Adaptive Form ? | Community
Skip to main content
M
monish_gavali
Level 3
May 20, 2026
Solved

How to create a custom Time Bound Date of Birth Component and add in a Adaptive Form ?

  • May 20, 2026
  • 2 replies
  • 31 views

I want to create a Time Bound Date of Birth Component, may be by extending the datepicker aem form core component, where user is allowed to select a date between a specific date range, so once i have created this component then i want to use it inside the adaptive form, but how can i do this, i dont see any AEM forms core components under /apps/core/fd…., i am trying to install the latest service package and the forms add on package my instance is breaking, Kindly help here

Best answer by Pranay_M

Hi ​@monish_gavali,

Thank you for your patience while we investigated this.

We reviewed both the Date of Birth component requirement and the issue with the AEM instance breaking after installing the latest Service Pack and Forms add-on.

Findings

1. Time-bound DOB component The Adaptive Forms Date Picker Core Component supports minimum and maximum date validation, so it can validate whether the selected date falls within an allowed range. However, if the requirement is to prevent users from selecting out-of-range dates directly from the calendar UI, this is not fully supported out of the box and would require a custom customization of the Date Picker Core Component.

For this use case, the recommended approach is to create a custom component based on the Adaptive Forms Core Component framework and use it in the Adaptive Form. This is typically done by extending/customizing the component within the project, rather than modifying product code directly.

2. Missing Forms Core Components under /apps/core/fd On AEM 6.5, not seeing Adaptive Forms Core Components under /apps/core/fd is not necessarily an issue. These components are typically enabled through an AEM Archetype-based project and consumed using the proxy component pattern, rather than being expected as a directly available product-owned structure in /apps/core/fd.

3. Instance breaking after Service Pack / Forms add-on installation The behavior you described is most likely due to a version alignment or installation sequence issue. For AEM 6.5, the supported approach is to:

  • install the AEM 6.5 Service Pack first
  • then install the matching AEM Forms add-on package for that exact Service Pack level
  • allow the instance to fully stabilize before proceeding further

If the Forms add-on does not exactly match the installed Service Pack, or if the installation is interrupted/incomplete, the instance can become unstable or fail to start correctly.

Recommended next steps

We recommend the following:

  1. Verify the exact AEM 6.5 version and Service Pack installed
  2. Verify that the Forms add-on package matches that exact Service Pack
  3. Reinstall using the supported sequence:
    • base AEM / confirmed stable instance
    • AEM Service Pack
    • matching Forms add-on
  4. Enable Adaptive Forms Core Components using an Archetype-based project
  5. Implement the DOB field as a custom component built on top of the Adaptive Forms Core Component model if calendar-level date restriction is required

Current recommendation for the DOB requirement

If the immediate goal is functional validation only, you can use the standard Date Picker with min/max validation and custom validation messaging.

If the goal is stronger UX — for example, users should only be able to select eligible DOB values directly from the calendar — then a customized Date Picker / DOB component will be required.

If you can share the following details, we can help validate the setup more precisely:

  • AEM version and Service Pack version
  • Forms add-on package name/version
  • Archetype version being used
  • whether this is local/on-prem/AMS

Best regards,

2 replies

A
akhil_merupula
Level 4
May 22, 2026

Hi ​@monish_gavali,


For a time-bound Date of Birth component in Adaptive Forms, you have two approaches depending on whether you're on foundation or core components.

 

Foundation Components (simplest path):
Use the out-of-the-box Date Picker and configure min/max constraints via the rule editor, no custom component needed. Set minimum date to "01-01-1900" and maximum date to today dynamically.


Core Components (custom extension):
The reason you're not seeing components under /apps/core/fd is that AEM Forms core components live under /libs/core/fd, you overlay them under /apps/core/fd/components. Make sure your project was generated with AEM archetype 41+ which includes Forms core components.


Service Pack breaking your instance:

The correct installation order is:
1. Install SP → restart → verify stability
2. Then install the Forms add-on package

 

Installing the add-on before the instance is fully stable after the SP is the most common cause of breakage. Also confirm your SP version and Forms add-on version match exactly.

 

What AEM version and service pack are you on? That will help narrow down the exact approach for your setup.
 

P
Adobe Employee
Pranay_MAdobe EmployeeAccepted solution
Adobe Employee
May 25, 2026

Hi ​@monish_gavali,

Thank you for your patience while we investigated this.

We reviewed both the Date of Birth component requirement and the issue with the AEM instance breaking after installing the latest Service Pack and Forms add-on.

Findings

1. Time-bound DOB component The Adaptive Forms Date Picker Core Component supports minimum and maximum date validation, so it can validate whether the selected date falls within an allowed range. However, if the requirement is to prevent users from selecting out-of-range dates directly from the calendar UI, this is not fully supported out of the box and would require a custom customization of the Date Picker Core Component.

For this use case, the recommended approach is to create a custom component based on the Adaptive Forms Core Component framework and use it in the Adaptive Form. This is typically done by extending/customizing the component within the project, rather than modifying product code directly.

2. Missing Forms Core Components under /apps/core/fd On AEM 6.5, not seeing Adaptive Forms Core Components under /apps/core/fd is not necessarily an issue. These components are typically enabled through an AEM Archetype-based project and consumed using the proxy component pattern, rather than being expected as a directly available product-owned structure in /apps/core/fd.

3. Instance breaking after Service Pack / Forms add-on installation The behavior you described is most likely due to a version alignment or installation sequence issue. For AEM 6.5, the supported approach is to:

  • install the AEM 6.5 Service Pack first
  • then install the matching AEM Forms add-on package for that exact Service Pack level
  • allow the instance to fully stabilize before proceeding further

If the Forms add-on does not exactly match the installed Service Pack, or if the installation is interrupted/incomplete, the instance can become unstable or fail to start correctly.

Recommended next steps

We recommend the following:

  1. Verify the exact AEM 6.5 version and Service Pack installed
  2. Verify that the Forms add-on package matches that exact Service Pack
  3. Reinstall using the supported sequence:
    • base AEM / confirmed stable instance
    • AEM Service Pack
    • matching Forms add-on
  4. Enable Adaptive Forms Core Components using an Archetype-based project
  5. Implement the DOB field as a custom component built on top of the Adaptive Forms Core Component model if calendar-level date restriction is required

Current recommendation for the DOB requirement

If the immediate goal is functional validation only, you can use the standard Date Picker with min/max validation and custom validation messaging.

If the goal is stronger UX — for example, users should only be able to select eligible DOB values directly from the calendar — then a customized Date Picker / DOB component will be required.

If you can share the following details, we can help validate the setup more precisely:

  • AEM version and Service Pack version
  • Forms add-on package name/version
  • Archetype version being used
  • whether this is local/on-prem/AMS

Best regards,

Terms & ConditionsAccessibility statement

Loading footer...