...

Implemented Transformer

BasicTransformer

BasicPropertyHandler

The property linked to a field is retrieved and stored based on the Field's  property name defined in the field definition.

A new property is created in case id does not yet exist.

...

In addition to the CompositeField and SwitchableField default Handler Transformer, we provide two an additional CompositeHandlerTransformer:

SubNodeCompositeHandler

 SubNodeCompositeHandler  will store the  property values of the fields composing the composite field under the following format:

...

...

formNode

...

...

Second field name composing the
Composite field

...

NoOpCompositeTransformer

NoOpCompositeTransformer

...

Third field name composing the
Composite field

...

This Handler do not support i18n (in Magnolia 5.1).

NoOpCompositeHandler

NoOpCompositeHandler is useful if you want to combine a Multi filed storing individual field value into sub nodes with composite field as Multi field component.

In this case, the Multi field handler field Transformer will createread/read write the node Item structure and pass a properties as PropertysetItem to the NoOpCompositeHandler NoOpCompositeTransformer. This handler This Transformer just act as a property container. 

MultiTransformer

MultiHandler

...

MultiValueTransformer

This is the default Handler default Transformer set for Multi value fields. The fields values are stored in a LinkedList<T> . This LinkedList<T> is then automatically convert to a JCR multi-value-property once it is persisted.
This will only work for simple fields like text/date/radio...

...

MultiValueJSONTransformer

Handler storing Transformer storing the fields values as a String with ',' as separator.
This will only work for simple fields like text/date/radio... and values are stored as String.

...

MultiValueChildrenNodeTransformer

HandlerTransformer storing the fields values in sub node item property: (Equivalent Jcr Structure of the form Item)

...

Limitation

How to

Open Issue

Default value handling

The field definition allows to define a default value as a String:

• Text field, type is String default value is 'default value'
• Text field, type is Long default value is 1000l
• ....

This default value should be displayed in the related form field if ????

• It is a new Form
  
  • easy to implement
  • if a field is added to an existing form, this default value will never be displayed.
  • chooses solution
• If the property related to a form is null (currently if a property has an empty value, this property is removed or not saved)
  
  • easy to implement
  • if a user remove the default value associated to a field --> no property saved. When he will reopen this form, the default value will be displayed again
• ??

...