Orbeon Forms 2018.2.3 PE

Today we released Orbeon Forms 2018.2.3 PE. This update contains bug-fixes and is recommended for all Orbeon Forms 2018.2 PE, Orbeon Forms 2018.2.1 PE and Orbeon Forms 2018.2.2 users.

This release addresses the following 40 issues since Orbeon Forms 2018.2.2 PE:

Security

• Remove YUI menu component for CVE-2010-4710 (#3972)
• Possible jackson-databind vulnerabilities (#4006)

Form Builder:

• JavaScript error in Form Builder when opening section (#4011)
• XBL component with `fb:template` causes exception when opening Form Settings dialog (#4027)
• In Form Settings, support components that don't create/remove attributes with listeners (#4030)
• Failing to add iteration to top-level repeated section containing a section (#4032)
• Inserting iteration before causes "illegal state when comparing controls" (#4035)
• NPE when opening Form Settings if inspector is enabled (#4055)

Form Runner:

• Form controls
• Dates with `+01:00` are not recognized (#4005)
• Support users typing dates without separators (#4021)
• fr:datetime fails to parse date in some cases (#4029)
• `fr:time` to support placeholder (#4037)
• Show `not-allowed` cursor when over date picker for read-only date (#4020)
• Form Builder control settings: support specifying "no grouping separator" (#4024)
• fr:number: incorrect formatting with pseudo-decimal point (#4026)
• Embedding and Liferay support
• Liferay 7: Liferay language selector portlet fails when in review mode (#3978)
• Issue loading class `HttpRequestInterceptor` with Liferay 7.0 Enterprise sp8 (#4009)
• Call `Liferay.Session.extend()` function upon Ajax calls (#4023)
• Proxy portlet and embedding JARs cause class loading error (#4001)
• Support Liferay 7.1 (#3959)
• Liferay proxy portlet randomly "swallowing" POST requests? (#3647)
• Other fixes
• Section titles must support HTML (#3671)
• Newly-relevant controls after repeat fail to update (#3976)
• Option to disable background on calculated fields with labels (#4004)
• New button has no effect (#3970)
• `fr:open-select1` not showing properly when printed in automatic PDF (#3979)
• Error when uploading files during auto-save with form with multiple attachment files (#4012)
• JavaScript error on iOS with date field in wizard (#4015)
• Initially collapsed and hidden section partially shows when it becomes visible (#4016)
• Autosave during upload can cause an error (#4003)
• fr:error-summary doesn't show error with section id ending with `-control` (#4022)
• Additional slash in TinyMCE theme URL leads to 404 on WebSphere (#4017)
• `type` element always missing on `xs:element` in generated schema (#4014)
• Schema generator option to produce type for maybe non-relevant elements (#4039)
• fr:synchronize-repeated-content: make `apply-defaults` configurable (#4038)
• Can't add a repetition to repeated section after the last one has been removed (#4018)
• Issue deploying on WildFly (#4045)
• "New from service" doesn't set data if there is no migration metadata (#4048)
• "Boolean Input" checkbox doesn't show in PDF (#4044)
• Help doesn't always show correctly in repeated grid (#4062)

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:

• via Twitter
• to the discussion list
• or as comments on this blog post

We hope you enjoy this release!

Summary page versioning support

Orbeon Forms supports versioning of form definitions. However, the behavior of the Summary page did not properly reflect that in a useful fashion.

Since Orbeon Forms 2018.2, when more than one form version is available, the Summary page now offers the user the choice of the version to access. This is important because different versions can behave like very different forms. This means that the search fields and the columns containing data can vary between form definitions.

Summary Page for version 1 of the form

Summary Page for version 2 of the form

When you change the form version using the dropdown selector, the Summary page automatically reloads the appropriate data from the database and updates the grids and search fields.

When navigating from the detail page to the Summary page, the appropriate version is also automatically loaded.

We hope you will like this Orbeon Forms 2018.2 feature. For more, see the documentation.

Field-level encryption

In Orbeon Forms 2018.2.2 PE, we introduced the ability for you, as a form author, to mark form fields as encrypted at rest, by simply checking a checkbox in Form Builder. When doing so, with no additional effort, the values of those fields will, at all times, be encrypted in your database.

Checkbox to mark field for encryption

You might want to encrypt the values of fields you deem sensitive, for instance to prevent access to those values even to a person who has access to your database, such as a database administrator, or a hacker in case your database server has been compromised. This feature can help you comply with data protection and privacy regulations, such as GDPR.

For more detailed information about this feature, see the page Field-level encryption in the Orbeon Forms documentation.

Form-level and control-level settings

With Orbeon Forms, some form controls have specific settings. For example, a Number field can be configured to show 2 digits after the decimal point. In the past, these settings could be configured in two ways:

• Using configuration properties, which could apply to a single form or or multiple forms.
• Using attributes in the source code of the form definition.

Neither solution was perfect. With Orbeon Forms 2018.2, we have improved this and you can now easily configure these settings through the Form Builder user interface:

• for all such controls appearing in the form definition,
• or for an individual form control in the form definition, in which case that local setting overrides the more general setting.

When neither type of setting is present, the configuration properties still apply.

This allows you to pick general defaults and change them as needed. For example, in general number fields have 2 digits after the decimal point, but in case a couple number fields need a specific setting, you can do that easily.

With Orbeon Forms 2018.2, this applies to the following built-in form controls:

• The "Number" and "Currency" fields support setting:
• a prefix
• a suffix
• the number of digits after the decimal point
• the decimal separator
• the thousands grouping separator
• rounding options
• the default field width ("full" or "natural")
• The "Date", "Time" and "Date and Time" fields support setting:
• the default field width ("full" or "natural")

The nice part is that this is done entirely through the Orbeon Forms component system. This means that it is possible to create new form controls which export metadata and editors which Form Builder will show in the "Control Settings" and the "Form Settings" dialogs.

For more details, see the documentation.

We hope you will like this feature Orbeon Forms 2018.2.

Orbeon Forms 2018.2.2 PE

Today we released Orbeon Forms 2018.2.2 PE. This update to Orbeon Forms 2018.2.1 PE contains bug-fixes and is recommended for all Orbeon Forms 2018.2 PE and Orbeon Forms 2018.2.1 PE users.

This release addresses the following issues since Orbeon Forms 2018.2.1 PE:

Form Runner:

• Regressions fixes
• Minimal repeated section - remove button doesn't work (#3948)
• Can't read encrypted data after server restart (#3961)
• Date and Time fields fixes
• Date input field to support `01` syntax in format (#3940)
• Date control does not switch to/from readonly with embedding (#3943)
• fr:date: insert above/below clears the date (#3957)
• Other fixes
• Saving fails for forms contains both a file attachment and encrypted field (#3931)
• Import: form version doesn't show (#3937)
• Import: validation status flag can be out of date (#3942)
• Email template fails when Explanation control is present (#3941)
• Email template with "All controls": attachment should show filename (#3947)
• fr:synchronize-repeated-content: "+" button doesn't work (#3956)

Form Builder:

• Setting Read-Only to "No" with a calculated MIP no longer works (#3950)
• fr:date: in Form Builder, you have to click exactly on the icon to pick a date (#3962)

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:

• via Twitter
• to the discussion list
• or as comments on this blog post

We hope you enjoy this release!

Improved date and time controls

Orbeon Forms 2018.2 features new Date and Time form controls.

The reason the controls are new is that we wanted to modernize the date picker on one hand, and add new features such as the ability to exclude certain dates from the date picker on the other hand. This would have been very hard to do with the older controls which had a lot of history behind them. So we created a brand new Date control, and we used the opportunity to improve the Time control as well. The new controls are implemented as XBL components, which means they are more modular and easier to maintain.

Here is the new date picker with the January 5, 6, 12 and 13 dates unavailable (grayed out) using The "Dates to Exclude" constraint.




In addition, the controls have an option to take their "natural" (usually more narrow) width or, which is new, to fill a grid cell entirely to facilitate alignment.




You control whether a field takes its "natural" width or the full cell width from the "Control Settings" dialog, or globally for the form in the "Form Settings" dialog.



Here is another example showing different control widths, adjusting automatically to grid cell widths.



For backward compatibility, only forms created with Orbeon Forms 2018.2 default to having full width Date and Time controls, while forms created before that version default to the "natural" width. This can be changed in the control or form settings, or globally via a configuration property.

The legacy Date and Time controls remain available for the time being for backward compatibility scenarios, but new forms created with Form Builder, as well as existing forms loaded and republished from Form Builder, will automatically use the new controls.

We hope you will like these enhancements of Orbeon Forms 2018.2!

Hidden fields

Orbeon Forms 2018.2 introduce a new form control in the toolbox called Hidden Field.

Now you might wonder why you would always hide a form field. There are two major use cases:

• Holding intermediary calculations:  If the control has a "Calculated Value" and/or "Initial Value" formula, it can be referred to by variable name (like $my-intermediary-result) from other formulas.
• Handling out-of-band validations: If the control has a label, alert and validations, a failing validation will show in the Error Summary. In addition, this also impacts the Wizard View's lax and strict validation modes, preventing forward navigation until the error is fixed by the user.

It has always been possible, with Form Builder, to hide any field by setting its visibility using the false() formula, or, with Orbeon Forms 2018.2, by selecting the option "No".

Control Visibility

But hiding a field this way can have unintended consequences. In particular, the control becomes in effect non-existent in the user interface when it comes to value change events which are useful in actions, and valid/invalid events which are used for validation. So even if the value of a non-visible control is invalid, the form is considered valid.

As a workaround, you can place a CSS class to hide a Calculated Value control to the user. The drawback of this is that the value of the control is still visible in the browser using "View Source" or development tools so this workaround cannot be used for sensitive data which the user should never see.

The new Hidden Field control, on the other hand, works like a regular control such as a Text Field in all respects, including events, validation, and alerts. Except, of course, that it doesn't show to the user at runtime. In particular, its value is guaranteed to stay on the server.

At design-time, in Form Builder, the control shows as a box with an icon so that the form author knows that a hidden control is in use. You can move that control and modify its properties like with any other form control.

Hidden Field in Form Builder

See also the documentation for details. We hope you will like this feature of Orbeon Forms 2018.2.