Versioning: show version on Form Builder summary page

[ebruchez]

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 to orbeon_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:

• support the notion of an "in progress" form definition
• also support regular FR autosave drafts
• support Summary page access in particular search

However, this is a big task.

In the meanwhile, we could choose a simpler path, as follows:

• form definitions keep a new "version" metadata
• this would show on the FB Summary page in a new column
• initially, this would be N/A
• upon Publish
  • about to be published version is stored in metadata
  • form definition is saved (2016-03-21: Since 2016.1 we save the form definition just before publishing.)
  • form is published
    • Q: What if this fails? Shouldn't have version metadata saved.
• upon editing
  • if there is no existing version, nothing to do
  • if there is an existing version, as soon as the user makes a change to the form, add a "changed" flag to indicate that the form has been changed
• Summary page shows column
  • N/A
  • 1
  • 1 with changes
  • 2
  • 2 with changes
  • etc.
  • only one row per app/form name at this time (although user can still duplicate / create new rows with same app/form name, see Prevent/warn creating form with same app/form name as saved or deployed form #818)
• edit source
  • we don't want to mess with the version by mistake here
  • before replacing source, copy form version metadata aside, and restore it
  • possibly allow user to edit last published version in edit form metadata dialog?

[ebruchez]

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:

• whether the form is available or not
• the version(s) the form is actually published under (/form should then also return version information, right now it doesn't, and this would also be useful for the FR Home page!)

[ebruchez]

+1 from customer

[ebruchez]

If doing this, could also do #1100 at the same time.

[ebruchez]

Moving to 4.8 now, but we might ship it as a patch to customer before that.

[ebruchez]

Putting back 4.8 milestone as this is relatively high on customer priority. To review with @avernet.

[ebruchez]

+1 from customer

[ebruchez]

+1 from customer

[ebruchez]

We still have two possibilities, possibly not exclusive:

1. What this issue is about, namely store a 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.
2. Using the Form Metadata API in the Form Builder Summary page to show the actual information about published form definitions and merge it.

Solution 1 appeared easier to implement, which is why we still considered it. See also this comment on #1138 regarding using stages.

[avernet]

About option 1 in #1795 (comment), 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