Chuyển đến nội dung chính

[CQ Embedded Form] Route to different pages after submit on CQ embedded form

Issue

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.

Solution

Use request.setAttribute(“cq.form.redirect”,”/content/myproject/en/thank-you-no.html”); in forward.jsp.

Detail

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.
By Feike Visser

Nhận xét

Đăng nhận xét

Bài đăng phổ biến từ blog này

[PERFORMANCE] Adobe WEM/CQ performance tuning

Adobe WEM/CQ performance tuning Contents Caching-related configurations CRX Bundle cache CRX Search index handler (Lucene) cache Tar PM index cache Scalability Maintenance Optimizing Tar Files (for Tar Persistence Manager) Data Store Garbage Collection Main documentation you should consult first: http://dev.day.com/docs/en/cq/current/deploying/performance.html http://dev.day.com/content/kb/home/cq5/CQ5Troubleshooting/performancetuningtips.html Caching-related configurations CRX Bundle cache CRX caches bundles, consisting of a node with all its properties. This is used by all bundle-based Persistence Managers. The default size of BundleCache is 8 MB. If this is too small it can cause an excessive number of read-accesses to the underlying persistence layer. Set the bundleCacheSize to something larger than the default. See more here: http://dev.day.com/docs/en/cq/current/deploying/performance.html#CRX%20Bundle%20Cache CRX Search index handler (Lucene...
Đăng nhận xét
Đọc thêm

[Query Builder] Advanced Search

Using the Advanced Search When using a list, select from the 'Build list using' options 'Advanced Search.' This will open a new tab in the list window with one text box labeled: 'Querybuilder Predicate Notation.' This is asking for a few lines of code to define search parameters. Example Code - With Explanations of Results Searching for Pages type=cq:Page property=jcr:content/jcr:title property.value=Places 'type' defines what sort of object you'll be searching for (it's usually a page). 'property' defines what property of the object you'll be filtering by; in this case, its by the title. 'property.value' defines your search term. So this search would be searching all PAGES with the TITLE of PLACES. So it would find every page titled Places. *IMPORTANT* Searches by title ARE case-sensitive, so 'Places' is not the same as 'places'. type=cq:Page path=/cq/sandbox property=jcr:cont...
Đăng nhận xét
Đọc thêm

[CQ6-SYSTEM] MAINTAINING THE REPOSITORY - Reduce repository size (cleanup repository)

Compacting Tar Files As data is never overwritten in a tar file, the disk usage increases even when only updating existing data. To make up for the growing size of the repository, AEM employs a garbage collection mechanism called Tar Compaction. The mechanism will reclaim disk space by removing obsolete data from the repository. Revision Clean Up By default, tar file compaction is automatically run each night between 2 am and 5 am. The automatic compaction can be triggered manually in the Operations Dashboard via a maintenance job called Revision Clean Up. To start Revision Clean Up you need to: Go to the AEM Welcome Screen. In the main AEM window, go to Tools - Operations - Dashboard - Maintenance or directly browse to http://localhost:4502/libs/granite/operations/content/maintenance.html Click on Daily Maintenance Window. Hover over the Revision Clean Up window and press the Start button. The icon will turn orange to indicate that the Revision Clean Up ...
Đăng nhận xét
Đọc thêm