This is the documentation for ConfiForms Server/Data Center app
However, this might also work for ConfiForms cloud and in most cases it does. But please see this page to understand the differences between server and cloud versions of the ConfiForms app.
You cannot downgrade from version 2.x to version 1.x automatically (without manually re-importing datasets with 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
Since ConfiForms app version 2.x we will publish release notes here
Experimental service to export ConfiForms data as RSS feed
https://<YOUR_SERVER>/ajax/confiforms/rest/export-to-rss.action? pageId=<PAGE_ID> &f=<FORM_NAME> &feedTitle=<FEED NAME> &feedDescription=<FEED DESCRIPTION> &feedLink=<FEED URL> &entryTitleField=<FORM FIELD TO USE AS TITLE> &entryDescriptionField=<FORM FIELD TO USE AS DESCRIPTION> &entryLinkField=<FORM FIELD TO USE AS URL> entryTitleField, entryDescriptionField, entryLinkField - could use virtual functions and access any field property your form's field may have Optional parameter: feedType Possible values: rss_2.0, rss_0.92, rss_0.94, rss_0.93, rss_1.0, atom_1.0, atom_0.3
Recovery API now physically deletes existing records and replaces the dataset contents with what's given. You can also clean up the form completely by uploading empty dataset in a format
{"data":"<list></list>"}
Enhanced service to check forms storage integrity (reporting non-compliant fieldnames)
[YOUR_CONFLUENCE_SERVER_URL]/ajax/confiforms/rest/storage-integrity.action?formName=<FORM_NAME>&pageId=<PAGE_ID>
Introducing "_func" bridge function to enable access to virtual functions through the entry (without using any field). This is sometimes necessary when you want to create complex dynamic filters such as:
field1:[entry._func.asEntryRef(entry.field2.transform(id).join( OR field1:))]
This filter, for example, tells to find records where "field1" values match values from "field2". And both fields are multi-value fields
Added support for "Apply filter" field definition rule to work on attachments picker
Assuming the field name for "Attachment picker" is "mypicker" and is set to show attachments from children pages, but you want to show only current page attachments (when you put FormView on a child page) mypicker.asAttachment.content.id:[entry._page.id]
Data migration is done for your automatically when you access the form for the first time. This could take some time for the first load, depending your your dataset size
There are methods to help you to understand how you data looks like and force the migration via migration APIs if you want to do so (accessible only to Confluence system administrators)
Storage analysis
[YOUR_CONFLUENCE_SERVER_URL]/ajax/confiforms/rest/storage-analysis.action?spaceKey=<SPACE_KEY>
Auto-migration
[YOUR_CONFLUENCE_SERVER_URL]/ajax/confiforms/rest/auto-migration.action?spaceKey=<SPACE_KEY>
Storage integrity check
[YOUR_CONFLUENCE_SERVER_URL]/ajax/confiforms/rest/storage-integrity.action?formName=<FORM_NAME>&pageId=<PAGE_ID>
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.
Your tables, rendered with CardView and TableView macros, will look different and use the cleaner styles as provided by AUI - https://docs.atlassian.com/aui/7.8.0/docs/tables.html
Your forms look cleaner as well, and also follow the guidelines and styles from AUI