List first so indexes are in expected order (#3736)max-width not to apply to label/hint (#3730) |
| Dragging cell boundaries horizontally |
 |
| Option to encrypt data at rest for a given form field |
 |
| Dynamic label |
 |
| Automatic calculations dependencies setting |
 |
| Dynamic email body |
 |
| Wizard status |
 |
| Wizard Options tab |
 |
| Attaching multiple PDF templates |
Securing web applications is always difficult and a moving target. Fairly recently, web browsers have started supporting the Content-Security-Policy HTTP header. This header is designed to help fight Cross Site Scripting (XSS) and data injection attacks.
Content-Security-Policy is very configurable. Some organizations set that header to strict values which disallow inline JavaScript and CSS within HTML pages. What this means is that anything like this is rejected by the web browser:
<script type="text/javascript">
function foo() { alert("Hello!"); }
</script>Up until Orbeon Forms 2017.2, Orbeon Forms includes some inline scripts and CSS in the HTML served to the browser. The purpose of this is, in particular, to provide some data and functions specific to the current form. So setting a Content-Security-Policy header which disables inline scripts and CSS would break Orbeon Forms.
With Orbeon Forms 2018.1 and newer, on the other hand, Orbeon Forms no longer produces inline scripts and CSS this by default. This can make Orbeon Forms safer by default if you set a stricter Content-Security-Policy.
In addition, and optionally, Orbeon Forms can generate the Content-Security-Policy header for you via a very simple configuration.
More details are available in the documentation.
We hope you like this new feature of the upcoming Orbeon Forms 2018.1.
Since the early days of Form Builder, all form controls are placed within grids. The basic idea of a grid, of course, is to have rows and columns. Until Orbeon Forms 2017.1 included, with Form Builder, each grid could have from 1 to 4 columns [1]. Spanning rows in a grid was possible, but spanning columns was not. This system served Orbeon Forms users well for a long time.
Orbeon Forms 2017.2 made an important change and introduced a 12-column layout [2]. What this means is that instead of varying the number of columns of a grid, you vary how many columns a control spans. So if you previously had a text area taking the entire width of a one-column grid, now you have a control taking 12 columns in that 12-column grid; a 4-column grid translates into a grid with controls each taking 3 columns, and so on.
You might wonder why we picked 12 columns. The answer is simple: the number 12 is divisible by 1, 2, 3, 4 and 6, and it is not “too small” or “too large” [3]. This means that it is possible to be backward-compatible with the previous 1–4 column system but also allows for more flexibility in the placement of controls since the granularity is now 1/12th of the width of the grid [4]. In short, using 12 columns is a good compromise.
| Grid Columns Orbeon Forms 2017.1 |
Column Span Orbeon Forms 2017.2 |
|---|---|
| 1 | 12 |
| 2 | 6 |
| 3 | 4 |
| 4 | 3 |
| 5 | 2 [5] |
| 6 | 2 |
With Orbeon Forms 2017.2, you can expand, shrink, split and merge cells with icons that show within each cell. And now with the upcoming Orbeon Forms 2018.1, we are enhancing the 12-column layout with drag and drop of cell borders. This means that you can resize a cell to take from 1 to 12 columns, depending on the cell’s location, instead of using icons.
And, in case you had missed, it, you can also drag and drop controls between cells now since Orbeon Forms 2017.2!
We hope that you will like these changes and the increased flexibility that comes with them!
With the option to extend that number at the risk of having funny-looking layouts. ↩
The 12-column layout applies to wider displays. For narrow displays like phones in portrait mode, each field shows on a single row. In the future, we can imagine separate configurations for other displays widths. ↩
Bootstrap grids use a 12-column system as well. ↩
Form Builder and Form Runner required major changes for this to happen. ↩
5 is not a divisor of 12, and so such rarely-used grid widths convert to 10-out-of–12 columns with changes we just introduced in Orbeon Forms 2017.2.2. ↩
