...
- Fixed issue when ConfiForms Field Definition Rules use [entry._page] in the filters / lookups and that points at the form's storage page, not at the page where the "form view" macro is located
- Fixed issue with incorrect rendering of non-latin symbols in user multi field
- Fixed rendering issue with TableView/CardView where certain fields have dynamically applied view restrictions and views were rendering with gaps
- Support for Scaffolding Live Templates as a possible source for ConfiForms macros (can load contents from the configured via LiveTemplates target page/template)
- Improved support for rendering rich contents fields when they are referenced through the smart fields. For example: that means we can render correctly a multi-page field that is referenced through the multi-select smart field (or any other type of smart field) as a nicely looking links to pages referenced
Version 2.16
- We are starting to implement protection mechanisms agains the XSRF attacks where possible and appropriate (https://developer.atlassian.com/server/confluence/form-token-handling/)
- Support for variables (via [entry.field_name] notations) in trunc/trim, truncLeft/truncRight and trimLeft/trimRight Virtual functions. Fixed trim*/trunc* functions to work and cut the value correctly
- Fixed issue with incorrect message encoding when record was updated from "inline edit"
- Improved support for field definition rules when used in inline modes (including a fix for field's re-initialization after "apply filter" rule was applied)
- ConfiForms IFTTT to delete entry (and update entries by filter) now supports dynamic parameters for form name and form's page location parameter
- Fixed issue with transformation of DB- and WS-backed dynamic multi-label fields
- Fixed issue with complicated expressions involving dynamic parameters referencing other field's value also dynamically. Something like:
...