AEM Forms (OSGI forms add-on on-premisies ) Core component "Dispaly Pattern" propery missing in Form core component dialogue | Community
Skip to main content
Level 5
March 4, 2025

AEM Forms (OSGI forms add-on on-premisies ) Core component "Dispaly Pattern" propery missing in Form core component dialogue

  • March 4, 2025
  • 1 reply
  • 1419 views

Hi Team

We are currently developing a custom Adaptive Form component using Core Forms Components. However, we are unable to see the "Display Pattern" option, which is available in Forms Foundation (Legacy) Components.

 

Problem:
In AEM Forms (OSGi forms add-on on-premises), when using Adaptive Forms Core Components, the Display Pattern property is missing in the Core Component dialog.


Regards

Vara




1 reply

rishim22446870
Adobe Employee
Adobe Employee
March 6, 2025

@varaandeIn Core Components, we use displayFormat instead of patterns for better performance. This is supported for date picker and number input components, as documented here:

https://github.com/adobe/aem-core-forms-components/tree/master/ui.af.apps/src/main/content/jcr_root/apps/core/fd/components/form/datepicker/v1/datepicker

https://github.com/adobe/aem-core-forms-components/tree/master/ui.af.apps/src/main/content/jcr_root/apps/core/fd/components/form/numberinput/v1/numberinput

Here are a few examples where this has already been used: https://github.com/search?q=repo%3Aadobe%2Faem-core-forms-components+%22displayFormat%22+language%3AXML&type=code&l=XML

Could you elaborate on your use case if you’re looking to apply this to the text input component?

You can also report such issues here: https://github.com/adobe/aem-core-forms-components/issues

varaandeAuthor
Level 5
March 24, 2025

Hi @rishim22446870 

I hope you're doing well. I am currently facing an issue with the Number Input component and its displayFormat functionality.

Use Case 1:
I’m trying to apply a display pattern/format (e.g., 00-001-1111), but the number input is displaying the value as 11111 instead of following the intended display format. Ideally, if the input includes preceding zeros, the display pattern should be applied in the same way as the Foundation or Legacy components handle text input fields.

Use Case 2:
I need to apply a display pattern/format for specific inputs, such as SSN (xxx-xx-xxxx), EIN (xx-xxxxxxx), or PTN numbers, which may contain characters but should still follow the display pattern.

It seems that the display pattern logic in the Number Input component is tied to the client library code, which is built at the component level.

Use Case 3:
We have a similar requirement where we need to apply the display format to text input fields since the inputs might contain characters, and the pattern needs to be applied accordingly.
(Ex : Preparer Taxpayer Identification Number (PTIN) : 1234-56P89)

How can we add a display format or pattern to an input text field? We copied the cq:dialog node for the display format, but it is not working since it is linked to the client library code. What is the best way to reuse the display format logic for input text?
How can we add a display format or pattern to an input text field? We copied the cq:dialog node for the display format, but it is not working since it is linked to the client library code. What is the best way to reuse the display format logic for input text?

I appreciate your assistance in resolving this.

varaandeAuthor
Level 5
April 2, 2025

@rishim22446870 

Thank you very much.
Customer Name :Internal Revenue Service(IRS.gov)

Regards

Vara


@rishim22446870 
Kindly advise  us alernative options binding the XDP to JSON schema for core component development Since AEM Forms Designer doesn't provide direct out-of-the-box functionality for binding JSON schemas to XDP forms.

Currently  Forms creating using xml schema then xdp is binding with xml schema but core component approach additon to json schema over complicated system . Please advise recommeded approach.