...

• 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 An 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

...