Dynamic Routing of “Thank You” Pages

In CQ you have the form functionality available that allows you to create a form on a page, for each form you can specify a “thank you” page that will be displayed when the form is submitted.

In this blogpost I will explain how you conditionally can route to different thank you pages depending on the values entered by the user.

Create a simple form
The first step here is to create a (simple) form to test the basic functionality.

You start with the “form” component, after this you can drag/drop other form-components like textfields etc in your form.

Configure the thank-you page

When you click “Edit” on the “Start of Form”, you can configure the “Thank You Page”, where the user will be redirected to after submitting the form.

So until now this is all out of the box functionality, the implementation of this you can see via CRXDE Lite via this path : “/libs/foundation/components/form”

In the advanced-tab you can choose the Action Type you want to use for your form after submitting the form.

In our case we will use the “Store Content” (default) action, that is implemented via this path : /libs/foundation/components/form/actions/store

Every “Action Type” consists out of some default JSP that can be found here : /libs/foundation/components/form/defaults/action

I will add some logic in the “forward.jsp” to implement the dynamic routing. For doing that I copied only the forward.jsp from /libs/foundation/components/form/actions/store to /apps/foundation/components/form/actions/store.

In the forward.jsp I added the following lines at the end of the file :

// added : if no was chosen for download, go to a different thank you page
// request.getParameter(“download”) will retrieve the value for the yes/no option
if ( “no”.equals( request.getParameter(“download”))) {        request.setAttribute(“cq.form.redirect”,”/content/myproject/en/thank-you-no.html”);
// end of added code

FormsHelper.setForwardPath(slingRequest, path);
request.setAttribute(FormsConstants.REQUEST_ATTR_REDIRECT_TO_REFERRER, “true”);

When you now submit the form and you choose “no” for download it will redirect you to a different page than when you choose “yes” for the download option.

Next steps:

This example is just to give you an idea where to make the changes if you have such a use-case.  If you have multiple forms then you have to consider extending or implementing an action whereby the author can specify the rules instead of hardcoding it.

About Feike Visser

Feike is an Adobe Marketing Cloud architect, working for Adobe Consulting in EMEA.
This entry was posted in Experience Services, ADEP. Bookmark the permalink.

Comments are closed.