Tuesday, September 27, 2016

Orbeon Forms 2016.2.1 PE

Today we released Orbeon Forms 2016.2.1 PE. This update to Orbeon Forms 2016.2 PE contains bug-fixes and important security fixes and is recommended for all Orbeon Forms 2016.2 PE users.

Specifically, this release addresses the following issues:
    • Form Builder
      • FB: Cut & Paste client side errors related to 'fb-static-upload-empty' control ID (#2935)
    • Form Runner
      • Database reindexing doesn't have any effect (#2921)
      • Relational: making form unavailable doesn't work (#2923)
      • ORA-01000 during reindexing (#2928)
      • form-runner-min.js not found (#2902)
      • Date picker buttons don't work with IE9 (#2893)
      • SQL Server: error with spaces doing full-text search (#2913)
      • 2016.2 "/> in process button rows (#2916)
      • Relational search: ignore `[1]` predicates (#2922)
      • When reindexing happens very quickly, the home page shows no progress indication (#2924)
      • Improve reindexing logging (#2927)
      • fr:datetime doesn't show as readonly (#2925)
    • XForms
      • XForms Server must not accept unencrypted payload (#2926)
      • Upgrade Apache Commons Collections (#2929)
      You can download the latest version of Orbeon Forms from the downloads page.
        Don't forget to grab a trial license for the PE version.

        Please send feedback:
        We hope you enjoy this release!

        Wednesday, September 14, 2016

        Versioning comments

        When using a relational database, Orbeon Forms supports versioning of form definitions.

        This means that you can publish multiple versions of a form known by its name (like the “ACME Order Form”). Data captured by, say, version 1 of the form can be viewed and edited with that version of the form, and data captured by version 2 of the form can be viewed and edited with that other version of the form, even if version 2 of the forms contains, for example, some additional fields. [1]

        With Orbeon Forms 2016.2, we added the ability for the form author to add a comment associated with a given version of the form definition.

        Why add a comment? A good reason is to include information about why that specific version of the form was created. The comment for the first version might just say “Original version of the form”, or remain empty. But the second version could include a descriptive comments of the changes introduced, such as “Added purchase order field”.

        You optionally set your comment when publishing from Form Builder: [2]

        If you choose to overwrite an existing version of a form definition upon publishing, the comment associated with that published version is loaded and you can decide to keep it as is or update it with new information:

        We hope you will find this feature useful! It is available in Orbeon Forms 2016.2.

        1. For more on form definition versioning, see:  ↩

        2. The comment is stored alongside the published form definition, not the form definition as you see it in Form Builder.  ↩