AF Core Component templates, theme is configured through a default config folder reference property sling:configRef not working

[varaande]

AF Core Component templates, theme is configured through a default config folder reference property sling:configRef not working(unlike AF foundation af templates, theme configuration for AF core component af templates is not exposed via template editor.)

For core component templates, theme is configured through a default config folder reference property sling:configRef at <template>/initial/jcr:content node level.
Refer below screenshot for <template>/initial/jcr:content 

[Sakshi5]

@varaande In templates, theme is aligned, how site page templates refer to theme, and it can't be changed. But you can change the theme once you create the form.

[varaande]

@Sakshi5 

If I understand correctly, it's currently not possible to set a custom theme client library at the core component template level in such a way that authors automatically inherit it when using the template—unless they explicitly select a different one.

We’ve observed that the default theme client library continues to point to:

/libs/fd/af/themes/corecomponents/canvas3-theme/clientlibs/forms-clientlib-site which resolves to "adaptiveform.theme.canvas3".

Below screen "Theme Client Libary " my intention to set to "dmaf.cc" Adative form Core Component Template level instead choose from dropdown list.

[pankajpr · Accepted solution]

Yes, at present the form creation wizard for 6.5 doesn't pick theme from the theme configured in the templates, it keeps canvas theme selected by default. User needs to change theme if he/she wants to use another theme.

[varaande]

@Sakshi5 
Is it possible to set a custom theme as the default in the Theme Client Library dropdown(workaround first option as project custom client libary categroy ) intenton or requirment is  authors don't accidentally select the Canvas theme (which is the default & s Foundation Components theme we able to set default theme )?

[Sakshi5]

This solution is for AEM Forms on Cloud:
@varaande Core component based forms currently support SiteConfig theme (check my other response).
In case you want to govern styling via clientlibs, you can add those to the page component (headerlibs). But again this will be a developer persona activity, and in this case authour will not be able to update it as well, unlike the proposed sling:config solution (check my other response).

So, yes you can set a default theme for template, but developer persona would need to create the theme.zip (like the sample themes [1] available in apps) or have a theme post execution of Front end pipeline and do the stitching of sling:configs (om.adobe.aem.wcm.site.manager.config.SiteConfig) with template  (check my other response)

[1] https://experienceleague.adobe.com/en/docs/experience-manager-core-components/using/adaptive-forms/s...

[varaande]

@Sakshi5 
So, this solution (setting default theme via template config) only works as expected in AEM Forms on Cloud, not in AEM 6.5 on-prem unless Prepare & Deploy Custom Theme.

[pankajpr]

@varaande, Yes, at present this is possible in AEM Forms on Cloud. We are working to improve 6.5 form creation UI to support picking up theme client library configured in the template.

[Sakshi5]

This solution is for AEM Forms on Cloud:
@varaande You can create templates with theme, by creating themes similar to reference themes we share, and create a sling:configs with child com.adobe.aem.wcm.site.manager.config.SiteConfig having property siteTemplatePath referring to apps path of theme zip (theme which you have created), under /conf/forms and link it with template, but this can be done via developer persona and not authour persona:
https://experienceleague.adobe.com/en/docs/experience-manager-core-components/using/adaptive-forms/s... 

Authour persona can choose the theme at time of form creation.