Gunter D'Hondt wrote:
Have you tried using multiple binding definitions (and multiple Binding
instances)?
You might also use 1 form and 1 binding but multiple form templates
(this might make it easier)
The disadvantage of using 1 binding is that you'll have to add and hide
all fd:fields in
Gunter D'Hondt wrote:
Have you tried using multiple binding definitions (and multiple Binding
instances)?
You might also use 1 form and 1 binding but multiple form templates
(this might make it easier)
The disadvantage of using 1 binding is that you'll have to add and hide
all
Here is how I did :
- 1 physical persistence file (ie where to bind data), but this could be
a bean
- as many definition, binding and template files as the number of pages
of the form. Each definition/binding/template batch maps only a
portion of the persistence file.
- a flow script that
Here is how I did :
- 1 physical persistence file (ie where to bind data), but this could be
a bean
- as many definition, binding and template files as the number of pages
of the form. Each definition/binding/template batch maps only a
portion of the persistence file.
- a flow script
