Experience Fragment - With a web form - Different Thank your page across different sites

[tcline]

Hello All,

This may be an easy solve or an attempt to use the wrong solution, so please correct us if you know of a better way! Also, we are not using any of the advanced Experience Fragment features like building blocks or variations in this case. 

Our quandary: We have chosen to use an Experience Fragment as an author controlled means to replicate a Web Form across multiple sites. Everything works well, except we can't seem to configure a site specific form submission "Thank You" page to work across each use of the XF. We *tried* setting the forms "Thank You" property to a generic relative path called, for example:  "ThankYou.html" and putting that page in the same folder as the page the EX form exists in each site. That unfortunately fails. It looks like under the hood the XF Form attempts to resolve the path for the ThankYou page and that fails because we didn't provide it a valid path.

Setup Outline and Desired Outcome:

Experience Fragment: Fully built form which has a Thank You page configured on submission.
Subsite 1: Page containing  the EF Form previously mentioned, In the same folder, Site specific Thank You page.
Subsite 2: Page containing  the EF Form previously mentioned. In the same folder, Site specific Thank You page.
Subsite 3: Page containing  the EF Form previously mentioned. In the same folder, Site specific Thank You page.

Desired Functionality: On submission of the page containing the form we would like to take the user to the site specific thank you page. 

Current Problem: Can't seem to configure an Experience Fragment with a site specific thank you page url as the form submission attempts to resolve the configured property and expects, I assume, a qualified path, not a pagename with no path like we are trying to use.

Is there a better or different way to solve this problem in an author-centric way? 

Many Thanks,

Tom.

[arunpatidar · Accepted solution]

you should look for context ware configuration.

1. Create an XF and configure generic thank you page.

2. Configure site specific configure page using context-aware-configurations.

[tcline]

Hello @arunpatidar!

Thank you for the answer. That sounds like a reasonable approach. Do you have any recommendations for a good setup guide on implementing context-aware-configurations? It is a feature we have no used yet, and from a quick review online I didn't come across and guides which connected all of the dots for me.

Thanks,

Tom.

[arunpatidar]

Installing context-aware-editor

• https://wcm.io/caconfig/editor/ 
• https://aemlab.blogspot.com/2022/06/aemaacs-tools.html 

Sample implementation

1. CAC is created via java https://github.com/arunpatidar02/aemaacs-aemlab/blob/master/core/src/main/java/com/community/aemlab/... 

1. Authored CAC stored in /conf (depends on https://github.com/arunpatidar02/aemaacs-aemlab/blob/25babe617e4b87422007db0993b0dc16f6b03458/ui.con...) e.g. https://github.com/arunpatidar02/aemaacs-aemlab/blob/master/ui.content/src/main/content/jcr_root/con... 

2. CAC Editor can be used by authors to see/update this value, CAC editor can be installed from all/pom.xml i.e. https://github.com/arunpatidar02/aemaacs-aemlab/blob/25babe617e4b87422007db0993b0dc16f6b03458/all/po... 

3. OSGi config https://github.com/arunpatidar02/aemaacs-aemlab/blob/master/ui.apps/src/main/content/jcr_root/apps/a... 

4. Then CAC can be read in Sling Model https://github.com/arunpatidar02/aemaacs-aemlab/blob/master/core/src/main/java/com/community/aemlab/... 

Note : CAC = Conteyt-Aware-Configuration 

[tcline]

@arunpatidar  - Thank YOU!

This is a perfect starting point - all of the guides I had found were from way back in 2017 and none outlined it so thoroughly.

I'll set aside some time and give this a shot!

Regards,

Tom.