AEM Forms - can Cloud Service Framework (for Analytics) and Launch integration be used/configured simultaneously

[m_alcantara]

We have AEM Adaptive Forms and would like to use the integration to collect data on form usage and submits, etc.

We've set up the Cloud Service Framework configuration described here:

https://experienceleague.adobe.com/en/docs/experience-manager-65/content/forms/integrate-aem-forms-w...

We also followed the steps to integrate Adobe Launch using the steps here:

https://experienceleague.adobe.com/en/docs/experience-manager-65/content/forms/integrate-aem-forms-w...

A Launch Rule was set up and published to fire on Form Submits using the steps as per the Launch instructions. The rule is not firing. In the meantime, the Analytics using Cloud Service Framework (first link above), is working. This configuration bypasses Launch, so it doesn't provide flexibility and control.

Use case:

I need to add an Action to the Form Submit rule in Launch to execute some code when it fires. This cannot be done via the Cloud Service Framework. Launch must be used to accomplish it. However, as mentioned, the Launch rule isn't firing.

Do we need to disable the Cloud Service Framework configuration and only set up the Launch integration? In other words, do we need to choose either one (the Cloud Service Framework configuration OR the Launch integration) for it to work? Or should they be able to co-exist?

Also, any other advise what else to look out for to get the Launch integration to work would be appreciated. Thank you.

[Harveer_SinghGi1]

Hi @m_alcantara ,

I'll suggest to perform few preliminary checks on your web page to make sure Launch configuration is loading correctly,

• Check if AEM Forms and Adobe Analytics extensions, data elements and rules created for this implementation are include in the library within the Launch environment that you are using for testing and that library is built (shows green dot next to its name).
• Check if Launch is loading on the web page, you can run _satellite command in browser console to confirm this
• Check if correct Launch property and environment (to which you built the library with needed implementation) is loading on the web page, run _satellite.property and _satellite.environment commands in browser console to check this
• Confirm if the intended rule is firing on the web page or not, to do this enable debugging on the web page run _satellite.setDebug("true") command in browser console before performing the form submit action, then submit the for and filter console for "fired" to see if the needed rule fired
• If the rule is fired and you still don't see an analytics call triggering then monitor the browser console for any errors related to the rule you configured, you can filter console logs for rule name

Perform all these steps and see if anything comes up.

Cheers!