...
- ConfiForms now has a new storage layer, with much faster edit and delete operations. And with faster and less memory consuming search / filtering operations.
There are no limits on the dataset size per form. And the size of the record is limited by the number of characters your database can hold in a CLOB type field (ConfiForms limits are 2,147,483,647 bytes) 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
Code Block [YOUR_CONFLUENCE_SERVER_URL]/ajax/confiforms/rest/storage-analysis.action?spaceKey=<SPACE_KEY>
Auto-migration
Code Block [YOUR_CONFLUENCE_SERVER_URL]/ajax/confiforms/rest/auto-migration.action?spaceKey=<SPACE_KEY>
Storage integrity check
Code Block [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
- ConfiForms is DC ready (approval is in progress)
- Optimizations in rendering: reducing HTML markup size → faster rendering
- All the features and changes included in 1.54.x releases, up to the latest 1.54.6, https://marketplace.atlassian.com/apps/1211860/confiforms-data-forms-workflows/version-history#b105004060
- Data is stored in the database table "AO_CEFA84_CONFI_FORMS_ENTITY", using record per row method.
- Rows are not physically deleted from the database when you delete a ConfiForms entry, but marked as deleted. Record contents is removed, but the ID and removal date for the entry are stayed. This allows us to "fix" the logic with auto-number re-use when last ConfiForms entry has been deleted (in ConfiForms version 1.x the last number will be reused, which is not the case anymore with ConfiForms version 2.x)
...