Page Flow Module provides a generic way to define and manage states of pages through Page Flow Documents in Bloomreach CMS authoring application, and a flexible way to implement Page Flow Interactions in Bloomreach CMS delivery-tier application.
What does it mean by Page Flow Interactions?
It is an application interaction style that comprises multiple steps for users to navigate, view or fill in the forms to complete a business-meaningful action.
Suppose a visitor is coming from a link in a marketing campagin E-Mail message. The link can possibly lead the visitor to the landing page first. If the visitor feels okay with the landing page content, then the visitor might want to follow the next page link. The navigation might lead to multiple step pages such as selecting a product, entering visitor's information, and so on.
Page Flow Module provides a solution to manage and implement this kind of multi-step-pages user interactions very easily in Hipppo CMS.
Why should Page Flow Module be introduced then? Can developers not use Enterprise Forms or something similar?.
If you asked this as well, that's really a good question!
You can use Enterprise
Forms or something similar for that kind of multi-step
interactions, but that's not multi-step-pages actually because that kind of
multi-step interaction solutions are working in an HstComponent
window level, not in multiple, totally-separated HST pages.
The multi-step interaction solution in an HstComponent
window level has the following disadvantages:
HstComponent
window level.HstComponent
window.HstComponent
window.Page Flow Module provides solutions for all those problems listed above.
PageFlowControl
implementationSiteMapItemHandler
implementation,
org.onehippo.forge.pageflow.hst.sitemapitemhandler.PageFlowControlHstSiteMapItemHandler
,
handling active PageFlow
and automatic redirection based on the states of PageFlow
.ChannelInfo
interface for Channel Manager.