...

Since ConfiForms app version 2.x we publish release notes here 

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

[entry.date.startDate.timestamp.add([entry.periodicy.multiply(86400000)])]-[entry.date.endDate.timestamp.add([entry.periodicy.multiply(86400000)])]

• Extracting page properties now supports when page property names are given as table headers (not only as 1st table column within TD element, but also could be given as a header, via TH element)
• Fixed issue with calculation of averages in TableViewMerger
• Fixed UI glitch when "use as proxy" parameter was not correctly rendered in macro browser in "Webservice Object Referencing Field"

Version 2.15.8

• Fixed issue with incorrect encoding and escaping of cyrillic/umlauts in validation messages (affects custom validation rules, field definition validation rules/messages)
• Now explicitly using UTF-8 encoding when serving pages lookups in the results provided by connected web-services (when used via ConfiForms proxy, affects fields that have "proxy" mode)

...