@varaande Basically you need a node under wizard, to make the component editable in authouring. You can make it part of your cq:template of your custom wizard. Anything changed in authouring will be then saved on that node.

@varaande Can you first try enabling the component via template and see if that is editable. If it is not then there is an issue with component definition. Otherwise just adding the component in cq:template would make it work. As Wizard navigates through all its children.Also we would be keen in kno...

Hi @varaande , You will need to go to template and allow the custom component in content policy of wizard.

@DavidNg6 Which version of 6.5 are you on?Core components on 6.5 is supported from 6.5.16 or later.Just change the  -D aemVersion="6.5.15" in the archetype command to generate project for specific AEM service pack. 

@aravindS Can you check if you are not using any ES6 syntax in custom function.Also can you try withAEM SDK v2025.5.21005.20250522T173058Z-250400andAEM Forms add-on v2025.04.29.00-250400

Hi David,Since you are referring to 6.5 article, I am assuming you are on AEM 6.5.Can you check if the forms core component bundles Adaptive Forms Core API (com.adobe.aemds.guide.aemds-guide-core) and Adaptive Forms Core Implementation (com.adobe.aemds.guide.aemds-guide-core-impl) are active?Update:...

And can you check that if only one version, that is, 3.0.104 version is there for both these bundles:AEM Forms Core Components - AF Core Bundle com.adobe.aem.core-forms-components-af-coreAEM Forms Core Components - Core Bundle com.adobe.aem.core-forms-components-coreand these bundles are also active

@SwathiSa6  If we have changed the import-package in configuration for bnd-maven-plugin, how come this bundle is still importing older version? Can you clean the target in the project manually and re-build the bundle, because it should have updated the imports.

Did you modify the import-package for this bundle? What is current import-package of bundle? Since this bundle is dependent on <artifactId>core-forms-components-af-core</artifactId>, for com.adobe.cq.forms.core.components.models.formYou will need to get the version updated to 3.0.104, as that dictat...

Is the issue resolved now?