jahiaone 2015 - form factory, architecture and extension points

Form Factory

Architecture & extensions

© 2002 - 2015 Jahia Solutions Group SA


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

History


Architecture


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

New Architecture


Creation Translation Publish Results Analytics

Lifecycle Management


Inputs are nodes All the definitions also

(input/validation/actions/popovers/renderers)

Inputs define their associated wizard

Forms are composed of input steps and a list of actions

Form Builder Architecture


Forms are validated client side Form tokens and captcha on

the server side Actions are responsible for

transforming/storing/redirecting the user after submission

Data can be stored in the JCR or not (only storage available in the core)

Submissions


Results Provider bound to backend type

Provide 1..* RESTful API

Views are bound to a RESTFul API

Results Analytics


Extend Form Factory


Define new inputs types Add custom wizard

options Extensions can be

used/deploy on a per site basis

Extends Inputs


Add validation wizard in the builder

Create JS rule compatible with Backbone.Validation

No server side validation apart token

Extends Validations


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

Extends Actions


Provide renderers for your inputs

Define new RESTFul API

Define new Reports

Extends Results

jahiaone 2015 - form factory, architecture and extension points

Technology