I have integrated Adobe Launch with AEM 6.4 and I am having issues with updated Launch config to be shown on AEM.
AEM and Launch integration has been setup
Steps to produce issue:
After performing steps above, I can see the following changes in AEM:
As a result, the site that was configured to use Adobe Launch did not get the latest changes.
Is this a bug or is there something else needs to be done to prevent this?
Ok, after playing around a bit more, I can observe that this is a "normal" behaviour.
So after a library update is published / build in Launch, it seems like it requires to launch the Adobe Launch Library Download workflow twice on AEM before the libraryUrl correct itself.
The only thing pending is that the rule using the Core library to run Custom Code is not running on the page.
Also, for the initial issue:
- Is this the normal behaviour?
For me, basic alert function did worked. I am not very sure about how Launch let JS work inside the web page.
Adobe Launch is to insert Tags into to web pages and retrieve the values the web-page. I am not very sure if using Launch for setting would be best practice. If you aim is to save some edited/appended value to the existing page title then that you can easily so by using Data Elements in Adobe Launch.
Jantzen.Belliston Adobe Launch expert need to intervene here to clear some more doubts here.
I tried running the following custom code:
Using the Core extension:
And the rule is just simply:
When I look at the source of the Launch script, I can see the Rule that I have setup above and it references another JS file with the following code:
However, the page is not executing the script as I cannot see the page title change.
Can you please let us know how are you trying to run custom code?
I have added an alert message in this example  and it is working fine for me.