You cannot downgrade from version 2.x/3.x to version 1.x automatically (without manually re-importing datasets with a recovery APIs) Upgrading from 1.x to 2.x is done for you automatically, with data migration. See release notes for the version 2.0.1 We advise you to take extra care with upgrading to version 2.x+ from 1.x branch and test your form configurations in your test environments first, before upgrading your live environments. |
If you have any questions about upgrading to ConfiForms version 2.x or have any issues, please contact us via Support Request Form See also Known issues |
Development versions could be found here: http://vertuna.com/builds/ |
If you are planning to update to latest LTS or latest 8.2.x/8.3.x version of Confluence and have ConfiForms forms with a number fields that exceed 256 then please vote for this issue to be fixed https://jira.atlassian.com/browse/CONFSERVER-88259 and the workaround suggested
If you are using Confluence 8.4.1 and later then please see this bug https://jira.atlassian.com/browse/CONFSERVER-92486 and the workaround suggested
Basically to make ConfiForms work as you use to on Confluence 8.x you will need to have at least the following properties adjusted/added into confluence.cfg.xml
These allow the forms to have 1000 fields and the field value accepted could be more than 100000 bytes You may adjust those to your needs, see https://jira.atlassian.com/browse/CONFSERVER-88259 and https://jira.atlassian.com/browse/CONFSERVER-92486 for the details |
Since ConfiForms app version 2.x and version 3.x we publish release notes here
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
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) |
/rest/confiforms/
1.0/excel/{attachmentId}
/rest/confiforms/
1.0/excel2007/{attachmentId}
/rest/confiforms/
1.0/csv/{attachmentId}
The option can also be enabled only to users in a specific user group/groups
cfSetValueWithEventPropagation from JavaScript functions is fixed to use the eventType and correctly propagate the event
Important! Downgrading from 3.7.0 will not be possible for ConfiForms installations which have web-service and db connections configurations. As the configurations are now encrypted and stored in an encrypted way (which is not supported by earlier versions of the plugin) |
You need to use a minimum Confluence version 8.0.2 (8.0.0 and 8.0.1 have critical bug https://jira.atlassian.com/browse/CONFSERVER-81454)
Available for manual install and downloadable from here. Compatibility range 7.0.0-8.0.2 (except Confluence versions 8.0.0 and 8.0.1 as per above)
Final 3.0.0 version of ConfiForms has been published on Atlassian marketplace and could be installed from there or from within Confluence UPM itself - https://marketplace.atlassian.com/apps/1211860/confiforms-data-forms-workflows?tab=overview&hosting=datacenter |
Release Notes for ConfiForms version 2.x (history) |