Can you upgrade the 6.5 service pack? If that’s not possible, please raise a hotfix request with Adobe Support to resolve this issue in 6.5.21. Also, does this issue have any functional impact?

Could you please confirm whether the resource type /libs/fd/af/connectors/rendercondition/marketo exists on your AEM instance? If it does, try enabling the feature toggle FT_FORMS-9611 to see if it resolves the issue.

@sarikajain From the stack trace, the exact root cause isn’t clear. Please verify that there aren’t multiple versions of the af-core bundle installed. Additionally, upgrade your Core Components to the version listed in the system requirements here and check if the issue persists:https://github.com/a...

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

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

@dpkhmhsBased on the screenshots you shared, it appears you're using foundation components to build the adaptive form. We recommend using the forms core components available through the AEM project archetype for creating adaptive forms.Could you please switch to using the core components for this us...

@SyedWa3The reason for this approach is that the name attribute of each radio button group must be unique. If it's not, the submitted data would be identical for all radio button groups. There are scenarios where forms may include radio buttons with the same name attribute across different panels or...