...

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

Version 2.25.5

• Disabling strict validating for form's configurations allows you to continue to use field names that differ with system fields by case (although, it is highly recommended to have field names that are different to internal field names each ConfiForms record has Documentation)

Version 2.25.4

• Fixed issue with inline edits of smart multi-row fields
• Field Definition Rules now work on a from rendered via Entry Viewer as well (same as with FormView)
• Fixed issue with incorrect event being sent when a record is changed through Smart multi-row field
• ConfiForms Registrations Control (FormView) macro's restrictions parameter supports variables and [entry.field_name] notations now
• ConfiForms EntryViewer's field name parameter supports complex expressions and [entry.field_name] notations as parameter
• ConfiForms file field now allows to clean up "broken file references". When the file was uploaded using ConfiForms, but has been deleted (directly) using Confluence.
• Templates can be looked up by space key as well, in addition to [template.TEMPLATE_NAME] you can use [template.SPACEKEY::TEMPLATE_NAME]
• Workaround for forms that have validation rules around fields that upload image files - Confluence has a bug that prevents ConfiForms from deleting the image file due to a DB constraint. We attempt to workaround this, but this will not work for scenarios when another version of a image file is uploaded (attachment with the same name) - in this case we skip deleting of this file to successfully complete ConfiForms process (as otherwise Confluence raises a transaction rollback)

...