Open ebruchez opened 10 years ago
See also #1138. The idea there was to run, on the FB Summary page, the /form API. This would allow us to show information which is directly in sync with published forms:
/form
should then also return version information, right now it doesn't, and this would also be useful for the FR Home page!)If doing this, could also do #1100 at the same time.
Moving to 4.8 now, but we might ship it as a patch to customer before that.
Putting back 4.8 milestone as this is relatively high on customer priority. To review with @avernet.
We still have two possibilities, possibly not exclusive:
last-published-version
metadata in the form definition. This as the benefit of simplicity, but the drawback of possible in correctness, for example if a form definition is published separately via the Publish API instead of directly from Form Builder.Solution 1 appeared easier to implement, which is why we still considered it. See also this comment on #1138 regarding using stages.
About option 1 in https://github.com/orbeon/orbeon-forms/issues/1795#issuecomment-1086395852, I also favor ease of implementation, but it looks to me like such denormalization would create a number of issues down the road, in what we could think are corner cases, and I'd bet sure some customers will hit those corners ;). For instance, this information stored in the "Form Builder form definition" might get outdated on a remote when a new form definition is published from the Form Runner home page, or something changes at the databases-level or database-configuration-level (properties-local.xml
changed to point to a different database for published forms, backup of published forms restored…).
tl;dr -1 on storing last-published-version
metadata in the form definition
Currently, the Form Builder Summary page doesn't show any published form version information.
One reason for this is that Form Builder deals with data stored in
orbeon_form_data
, and only pushes toorbeon_form_definition
upon publish. So it doesn't have any information about published forms. This has been found confusing to some, BTW.One way to change this would be to have FB only deal with
orbeon_form_definition
. We would need to:However, this is a big task.
In the meanwhile, we could choose a simpler path, as follows: