The document discusses the evolution of the form builder architecture from Jahia Solutions Group, addressing usability issues in previous versions and outlining improvements in a new architecture. It highlights lifecycle management, client-side validation, and the ability to extend the system with custom inputs, validations, and actions. Additionally, it emphasizes the integration with RESTful APIs for form submissions and analytics reporting.

1. Form Factory
Architecture & extensions
© 2002 - 2015 Jahia Solutions Group SA

2.  Form builder was designed to
create form using GWT engines
 This lead to a lot of boxes in each
other
 Form were not easy to reuse/find
as they were not centralized
 Results were stored under the
form itself in live mode only
© 2002 - 2015 Jahia Solutions Group SA
History

3. Architecture
© 2002 - 2015 Jahia Solutions Group SA

4.  Site settings App
 Form management through
a form library
 Form results weakly bound
to the form itself
 No GWT engine
 Extensible with other
modules
 Analytics reports of results
© 2002 - 2015 Jahia Solutions Group SA
New Architecture

5. Creation
Translation
Publish
Results Analytics
© 2002 - 2015 Jahia Solutions Group SA
Lifecycle Management

6. Inputs are nodes
All the definitions also
(input/validation/actions/p
opovers/renderers)
Inputs define their
associated wizard
Forms are composed of
input steps and a list of
actions
© 2002 - 2015 Jahia Solutions Group SA
Form Builder Architecture

7.  Forms are validated client side
 Form tokens and captcha on
the server side
 Actions are responsible for
transforming/storing/redirectin
g the user after submission
 Data can be stored in the JCR
or not (only storage available
in the core)
© 2002 - 2015 Jahia Solutions Group SA
Submissions

8. Results Provider bound
to backend type
Provide 1..* RESTful
API
Views are bound to a
RESTFul API
© 2002 - 2015 Jahia Solutions Group SA
Results Analytics

9. Extend Form Factory
© 2002 - 2015 Jahia Solutions Group SA

10. Define new inputs types
Add custom wizard
options
Extensions can be
used/deploy on a per
site basis
© 2002 - 2015 Jahia Solutions Group SA
Extends Inputs

11. Add validation wizard
in the builder
Create JS rule
compatible with
Backbone.Validation
No server side
validation apart token
© 2002 - 2015 Jahia Solutions Group SA
Extends Validations

12. Actions are standard
Digital Factory Action
Backed up by a JCR node
of type “fcmix:action"
Wizard for the action is
defined in the JCR as it is
done for
Inputs/Validations
© 2002 - 2015 Jahia Solutions Group SA
Extends Actions

13. Provide renderers for
your inputs
Define new RESTFul
API
Define new Reports
© 2002 - 2015 Jahia Solutions Group SA
Extends Results