af2themeclientlib implementation not working with AEM Forms Cloud

[shravanthprasad]

Expected Behaviour

Should be able to create forms using af2clientlibtheme

Actual Behaviour

Need to create a theme and add it to the form while creating using a theme

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Latest AEM Cloud

AEM Version (mention the exact version in case of cloud SDK)

Adobe Experience Manager (2025.10.22943.20251009T135918Z)

AEM Forms Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

[rismehta]

@shravanthprasad The issue isn’t clear—could you please specify what exactly isn’t working and share more details?

[shravanthprasad]

@shravanthprasad The issue isn’t clear—could you please specify what exactly isn’t working and share more details?

@rismehta on AMS, we are able to select theme client library as shown below

but on AEM Forms cloud, this option changes and we can select only theme and not clientlibrary

We have a common code repository across both AMS and cloud and want to reuse the existing theme client library(as in AMS) approach.

[rismehta]

@shravanthprasad The issue isn’t clear—could you please specify what exactly isn’t working and share more details?

@rismehta on AMS, we are able to select theme client library as shown below

but on AEM Forms cloud, this option changes and we can select only theme and not clientlibrary We have a common code repository across both AMS and cloud and want to reuse the existing theme client library(as in AMS) approach.

In core components, the theming approach is different. On AEM 6.5, it is implemented as a client library, whereas on Cloud Service it is handled as a front-end asset. The steps to create a theme on Cloud Service are documented here:
https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/forms/adaptive-forms-authoring/authoring-adaptive-forms-core-components/create-an-adaptive-form-on-forms-cs/using-themes-in-core-components

The transformation should not take much time to complete.

[pankaj-parashar]

@shravanthprasad , the deployment artifact is different for both 6.5 and Cloud Service, but theme source remains the same.

theme source (repo) ------> create theme client library (6.5)
theme source (repo) ------> deploy via FE pipeline (CS)

In case of Cloud Service, you need to deploy the same theme repo via front end pipeline.

[shravanthprasad]

@pankaj-parashar @rismehta - Thanks for the inputs. For AEM 6.5, we have the theme client library built as part of maven module with the same repo. What is the theme.zip files that are generated as part of the aem project archetype? (https://github.com/adobe/aem-project-archetype/tree/72061a4fc9b098b423425058579a3a5a96690a30/src/main/archetype/ui.apps/src/main/content/jcr_root/apps/fd/af/themes)
we are looking to have the changes in the same repo and not create a separate repository for just themes as we do not have concept of themes for our forms, we have just one consistent brand design(single theme) across all forms.