Campaign standard: template from AEM

[gyorgyb62452513]

Hi,

Is it possible to pull in an e-mail delivery a template from AEM outside of /content/campaign? So far it seems /content/campaign is hard-coded in request ACS triggers to get the list of templates available in AEM. Is it configurable somewhere? Is it on radar to remove this limitation?

Thank you.

Best regards,

Gyorgy

[florentlb]

Hi Gyorgy,

If you are using the integration with AEM 6.1 or 6.2, there is an option in ACS (in Administration > Instance settings > Options) which is called AEMResourceFilter which defines the AEM content types to retrieve, as stated here: Integrating with Experience Manager 6.1 or 6.2 

Let me know if that would do the trick for you,

Florent

[gyorgyb62452513]

Hi Florent,

I have found this configuration, but unfortunately as I understood it is about resource types only. Am I right?

Our problem is the following: we are on AEM 6.2 (without any SP/FP) and we would like to use Template Editor for our e-mail templates pulled from AEM. We have so far see that it is hard coded that Template Editor is not available for pages under /content/campaign. If the e-mail templates are moved outside of /content/campaign, template editor works great, but then these templates cannot be accessed from ACS. ACS looks for templates under /content/campaign in AEM and it seems to be hardcoded. Is there a way to use different path?

Do you know if Template Editor somehow can be enabled under /content/campaign?

Thank you in advance.

Best regards,

Gyorgy

[florentlb]

Hi Gyorgy,

I'll send an internal note regarding this to see if there has already been things like that implemented. I'll let you know as soon as I get a reply.

Florent

[Kornel_Keseru · Accepted solution]

Hi Florent,

Meanwhile we found a way to implement our emails using editable templates (Template Editor) under /content/campaigns, see our summary on

Editable templates under /content/campaign

After these changes, ACS can pull in the emails successfully.

I understand that supporting emails outside of /content/campaigns would probably need changes in AEM's code, too, but removing the path restriction (/content/campaigns) from ACS could still give implementors a bit more flexibility on how the AEM content structure is established.

Thanks,

Kornel