Ability to specify a custom XML data model

[ebruchez]

We had initially planned to have this feature for 4.0, but then deprioritized it. At this point (4.3) the feature is disabled. For reference, here is the list of related open bugs as of 4.0. However, they are probably more bugs now.

We need to decide how best to implement this feature. Should we follow the approach taken for 4.0? Or is there another way?

Also, do we actually need a full custom XML data model, or is there a middle way, whereby we could specify some options for the data model?

[ebruchez]

Here is a proposal for a different approach:

• Form Runner and Form Builder keep using the Form Builder-imposed data model
• this reduces the complexity as the Custom XML feature becomes more orthogonal to FB/FR
• as in pre-4.0 work, a custom XML template can be provided, and controls specify bindings
  • bindings might be XPath or a subset of XPath
• conversion is applied between the two models when needed
  • send to URL
  • read/write from persistence
• Form Builder should provides a UI to help provide the bindings
  • set the custom data model
  • enter a binding for a control, possibly listing the nodes in a tree selector and/or suggesting based on the control name and conversely
  • validate that all controls have bindings
  • validate that bindings point to nodes in the data model (warn/error if not)
  • ideally: quick way to review bindings

Open questions:

• persistence
  • does the data need to be persisted in the standard format, custom format, or both?
  • this has an impact on search too
  • A: there is a customer requirement for persisting at least in the custom format
• should the XML Schema generator service work?
  • A: currently no customer requirement, but ideally yes

[avernet]

+1 from customer

[ebruchez]

+1 from evaluator