Well, it took me a good few hours but in the end the culprit was the Marketo host configuration; instead of the host used to log in marketo (e.g. engage-lon.marketo.com) you need to use the app host (e.g. app-lon10.marketo.com)

Hi everyone, We have performed the Marketo forms integration into our local AEM as a Cloud Service author, as described in https://adobe-consulting-services.github.io/acs-aem-commons/features/marketo-form/index.html . However, when attempting to view the embedded form, the cmponent does not appear a...

Hi @Vinodthakur , Unfortunately no - eventually we just checked the WF instance node properties to get the failing status, so no direct indication of failure. Kind regards

Dear Community, Is the Feed importer feature available still on AEM? I tried using the classic UI but even that (at least using purely UI) does not seem to work. My questions here are:Is there a workaround for this, to make the feed importer work?If not, what is the best way to create a custom e.g. ...

indeed, the CSV-based approach is for cases where the glossary content is a bit more "raw". If you want to have an arbitrary set of editorial component you would probably go for a "Container" component + customization.

Suggested approach based on personal XP:Have the glossary terms + definitions in a CSV fileUpload the CSV in DAMGlossary component:Editorial dialog: Provide the DAM path to the csvSling model: extract glossary terms + definitions from csv on the fly. Alternatively, you can use AJAX requests (instead...

Hi @rsl_lucky , Did you already have a look at AEM Core components?

Hi @winstonl3651471 , Can't you either1. Use the "THEN" action builder to chain the firing of the tags twice?2. use 2 different rules to fire the tag using the extension (1 rule per firing)? You could even control their ranking to ensure proper order of firing the tags.

I think this question might be more suitable for the AEM section 

Judging from past experience, I would suggest starting small before making major repo changes to tackle the issue. What version of AEM are you now using? Still 6.1? Indeed using a datastore for blobs is the suggested way (we often switched to S3 DS in the past) Are you using the OOTB maintenance tas...