@varaande Apologies for the delay.There may still be performance issues when handling 500 fields, even with core components in the form editor. To mitigate these issues, it's recommended to use fragments, as outlined in the best practices documentation.Although core components are generally more per...

@VARA_PRASADA_RAOAN2Thank you for providing detailed information about the use case. You can achieve this by using a JSON schema in the following manner:New Form Development Process Using Core Components: Create an XML schema-based manual PDF (XDP).Develop an AF (Adaptive Form) using the JSON Schema...

@varaande Why are you using XDP-based forms? Are you reusing specific rules from the XDP form, or is it primarily for the Document of Record (DoR)?If it's for DoR, you might consider using a JSON Schema-based form with the Auto Document of Record feature instead.We generally do not recommend XDP-bas...

Thanks, @varaande , for sharing the use case. I've logged an enhancement ticket to support these common scenarios natively in the product without requiring customization.For now, please use the format option in the Visual Rule Editor for this use case. I've attached a screenshot below. This feature ...

@varaandeThere's no need to copy fd:rules or fd:events for custom components unless your component includes default rules (which is part of cq:template) These are automatically generated when rules are created using the Rule Editor.You can refer to a working example of a custom Core Component here: ...

@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/...

@varaandeI just tested the same use case, and it worked fine. Here are the steps I followed:Copied the pattern and pasted it into the pattern option as part of the text input configuration in the edit dialog.Saved the configuration.Reopened the text input configuration and confirmed that the slash w...

Could you rename the 'uk' folder to 'en_GB' to align with the correct locale naming convention? The 'uk' code refers to Ukrainian, while 'en_GB' is the proper code for the United Kingdom.

Could you please log a ticket through the support channel to have this addressed in the foundation components? Also, kindly include the steps to reproduce the issue.

@dpkhmhsThis issue typically occurs due to slow form rendering, often caused by a large number of form elements or complex custom business rules. Could you please provide answers to the following questions:How many form objects are there in total (i.e., components dropped during authoring)?Are there...