...

Version 3.16.3

• Fixed issues with filtering engine when a value with dot(s) is given as a parameter for the free text search
• Added support for dynamically resolved values (via [entry.field_name] notations) for the following parameters in the ConfiForms Form Definition: to define additional super users and form administrators
• Extended func bridge to take an argument, this allows, for example, to do something like [entry._func(123456).asPage.pageProperties(myproperty)] - to read a page property value from a given page

Version 3.16.2 - internal version

Version 3.16.1

• Fixed issues with Confluence 9.x and rendering of barcodes, QR codes and captcha for anonymous users
• Support for @self and for @parent when referencing pages in smart and dynamic fields configurations
• "Divide" virtual function now respects the scale of a value that is used as a divisor when rounding
• Dynamic dropdown and dynamic multi-label offer choices immediately and dont require for users to start typing
• Whitelisted methods of a ConfiForms record (RegEntry class) to be able to use with Confluence 9.x with Velocity templates 
• ConfiForms action to Delete a Page (https://wiki.vertuna.com/display/CONFIFORMS/Configuring+ConfiForms+IFTTT+actions+and+rules#ConfiguringConfiFormsIFTTTactionsandrules-DeletePage) now supports an option to delete a page with descendants (full hierarchy) 
• Fixed issue with REST APIs using stalled data from the cache
• Fixed small issue with a Checkbox group not taking in the custom CSS style when configured
• Fixed issue with parsing of dates where custom format creates a numeric value

Version 3.16

• Fixed issue with a Link field compatibility with Confluence 9.1+
• Fixed issue with REST API module not enabling on certain versions of Confluence (8.8.x in particular)
• Fixed content type for exports in excel format
• Fixed issue with custom layouts not being correctly used for Edit Controls when they are configured with dynamically resolved properties ([entry.field_name] notations)

Version 3.15.10

• Fixed issue with an enabled parallel filtering and free text search on forms that have smart fields
• Fixed issue with forms having smart fields and "apply filter on fields" rules and preset values
• REST API uses cached results if available to speed things up and reduce impact on the database

Version 3.15.9

• Repackaged to support Confluence 7 and 8

Version 3.15.8

• Fixed issue with REST API double encoding of values for smart fields or multi-value fields

Version 3.15.7 - private version

• internal release

Version 3.15.6

• Fixed issue with filtering engine not correctly filtering values when parallel filtering is used and expressions have "queryAnd.." type of functions or use security groups related functions

Version 3.15.5

• Fixed issue with smart/dynamic fields when the configuration uses [entry._page] as a reference to the form's page
• Fixed issue with incorrectly cached list of records when loaded as smart fields choices

Version 3.15.4

• Improved handling of attachments "delete operation" when an attachment has multiple versions 
• Fixed issue with the parallel filtering when functions use thread context variables, such as current user, etc 
• Fixed issue with ConfiForms Filter Control macro's reset button not resetting the values correctly

Version 3.15.3

• Fixed issue with an inline edit and the action buttons on TableViews not refreshing the contents
• Fixed security issue with adding comments (comment field) even when the user has no view permissions on the form
• Web-service Request IFTTT now reports (only) the response as a result, when form is not in the debug mode

Version 3.15.2

• Improved parsing of complex expressions that involve replacement of values or use of evaluateFormula or iterateAndPrint functions
• Improved filtering engine performance by switching to parallel streams. This improved performance by 80-100% on certain form configurations

Version 3.15.1

• Fixed issue with a lost locale for the user doing the REST API calls which resulted in dates being parsed with a "server locale" which could have provided some unexpected results and deviations
• Fixed issue with NPE in filtering engine when used with multi-labels/multi-values fields
• Fixed issue with ConfiForms Filter Control when used with dynamic dropdowns and wildcards matching is enabled
• Fixed issue with Import API not working for datetime interval fields
• Lowered number of items to be processed asynchronously per thread when parallel loading / rendering or  filtering is enabled

Version 3.15

• Compatibility with Confluence 9.2
• Remote loading for smart fields (new parameter in the ConfiForms Field Definition): Advanced dropdown and the multi-select field. Useful for forms that use large amount of data
• Fixed issue with REST API create endpoint and mappings for the multi-value fields
• Optimized loading of forms that have fields that load large amounts of data into choice-based fields, but have rules that filter out those options initially
• Improved performance in filtering for multi-select fields and free text searches
• Fixed issue with setting the multi-user field not rendering the user's avatar

Version 3.14.4

• Compatibility issue with Confluence 9.x and ConfiForms CSS rules macro (blocked methods due to missing whitelisting https://developer.atlassian.com/server/framework/atlassian-sdk/configuring-the-velocity-allowlist/)

Version 3.14.3

• Fixed issue with forms having multiple file/attachment fields

Version 3.14.2

• ​Addressing CVE-2024-47072
• Support for base64 file uploads in ConfiForms Server REST API version 1 + extra endpoint to support base64 file uploads
• Fixed issue with permissions restricted fields being reported in the form's debug mode
• TableViewMerger with flattened mode the records now have an original entry ID value reported in a _originalId field 
• ConfiForms is now more strict on expressions that you use to access values and objects. Please make sure you use correct letter casing and naming. 
• Fixed issue with local notifications not working on Confluence 8.x

Version 3.14.1

• Fixed a regression issue with a virtual function when applied on one the object's properties (User, Page, Jira issue)

Version 3.14

• Fixed issue with conflicting dependency on Confluence 9.x which prevented the app from being enabled
• Repackaged to support Confluence 7.19.x as lowest version

• Warning

  Please note that ConfiForms is now more strict with the expressions that you have for filtering or accessing values - it does EXACTLY what you ask, and tries to provide the value for the property/field you ask.  Previous behaviour was as follows - the "latest resolved value" has been returned as a result. Now this has changed and ConfiForms will not do that, but will return the value for the property that you have asked For example - you have something like this: A dropdown field named "mySelect" and was having the expression like this Code Block [entry.mySelect.something] ConfiForms before the 3.14 will return a value for [entry.mySelect], ConfiForms version 3.14 and newer, will return an empty value, as there is no property as "something" in the dropdown field (see Accessing field values and properties), neither "something" is a function (Virtual functions)

Version 3.13.9

• Fixed issue with Import API not taking the custom delimiter parameter on Confluence 8.8+
• Fixed issue with license check and reporting of invalid licenses on ConfiForms data edits
• Fixed issue with autocomplete (off) functionality on Edge 
• Improved logic with complex forms that update fields via IFTTT rules when removing attachments
• Fixing dependency issue with Confluence 9.1
• Fixed issue with ConfiForms Filter control set on date intervals with an enabled "OR" condition
• Fixed lookup on a JiraSelectField, when cascading field is used as a source and the user wants to access a child property

Version 3.13.8

• Fixed issue with CSS on tables rendered via TableView (remote rendering - admin UI, pagination)

Version 3.13.7

• Fixed the Jira Select Field to work with Jira 9.x + support for ConfiForms Field Definition Rules#ApplyFilteronafield rule to work correctly on any number of fields and issue types (was taking the first 200 only)

...