...
What ConfiForms can do for me?
ConfiForms add-on app can help you to build data entry forms directly in Confluence, using Confluence editor. ConfiForms add-on is app is very versatile in functionality and covers a lot of user scenarios, with lot's of integration options - ranging from JIRA to databases and external web services. All these could be integrated into ConfiForms Form to help you to build a truly interactive user friendly forms.
...
ConfiForms add-on is developed and maintained by Vertuna LLC, established in 2005 and based in Estonia, Tallinn. We are Atlassian Verified partner (now the program is called Top Vendor) since , no called Silver level Atlassian partner) since 2015
You can contact us directly via the button below and we aim to answer you within 48 hours, but in most cases much faster 
...
ConfiForms stores data in your database, same database you Confluence is using. Where exactly depends on the version of ConfiForms you are using. If you are on version 1.x of ConfiForms please consider upgrading to Data Center ready and much more performant 2.x version of ConfiForms. Please see Release Notes for details
| Version | Storage |
|---|---|
| Version 3.x | Same storage as in version 2.x, see below |
| Version 2.x | ConfiForms stores data in your Confluence database in a table "AO_CEFA84_CONFI_FORMS_ENTITY", one record per row. There are no limits on on the dataset size per form . And the size of the record is limited by the number of characters in ConfiForms, but your database is limited to holding the total of 2,147,483,647 records (for all the forms). And the size of the record is limited by the number of characters your database can hold in a CLOB type field (ConfiForms limit is 2,147,483,647 bytes per record). |
| Version 1.x | ConfiForms stores data in page metadata table called OS_PROPERTYENTRY. Internally the data is stored as XML. As the data is stored as page metadata it becomes a part of Confluence standard backup and restrore procedure. But this also introduces the limits - we are able store (within one form) as much as the "text_val" field in "OS_PROPERTYENTRY" table can accomodate. You can have multiple ConfiForms, this limit is per form. For example, when Confluence uses MySQL database then this field type is MEDIUMTEXT which has a limit of 16MBs (which you can easily ALTER to be of a larger size). |
There are no limits on the number of forms and fields per form you can have.
ConfiForms cloud is different, see Data storage types: ConfiForms native vs Atlassian content properties
What is storage format?
When we ask you to provide us with a storage format for your page configuration - here this is what we mean.
| Server/Data center | Cloud |
|---|---|
|
|
It allows us to import the contents directly to our test server and see exactly the configuration you have, and to help you with troubleshooting the issues you might have, a lot faster.
Atlassian documentation on storage format - https://confluence.atlassian.com/doc/confluence-storage-format-790796544.html
How do I see the version of ConfiForms
This is easy when you already have a form (ConfiForms Form macro). It requires you to do the following 2 steps
How many records could I save into ConfiForms?
Below is valid for ConfiForms version 1.x
...
Where do I see the license SEN for ConfiForms
Same as with ConfiForms version - see above. You create a simple form and then use "Admin UI" to show you the stored data (View/Edit stored data). And the table footer will display the SEN and the version number for you
How many records could I save into ConfiForms?
| Info |
|---|
With ConfiForms version 2.x there are no set limits on the number of records. See Where ConfiForms stores data? |
Below is valid for ConfiForms version 1.x
We do not have any hard limits but you have to understand that ConfiForms is not a replacement to JIRA and storing support cases in thousands and having hundreds of concurrent users accessing the same forms datasets is not what it is designed for. However, we have seen installations where ConfiForms holds 5000+ records in one form. Not recommended, but possible (See also the Q/A above). We suggest to split your data into multiple forms, have an archiving in-place using IFTTT macro and try to keep your busy ConfiForms with small datasets. Please also note that complex forms with many fields (like 100+) will need more space to hold for one record.
Some numbers to share (very old (for version 1.x), and has been improved with new releases):
| Records # | Fields # | Data size | Form rendered | Data loaded | Edit entry dialog | Admin UI all records (TableView rendering) | Rendered size (of HTML for admin UI) | All records filtered by one field, no edit controls | All records with sorting (3 fields) with Edit controls | All records, no sorting, no Edit controls | Paged view, 50 records per page sorted, and with edit controls | Paged view, 50 records per page sorted, and no edit controls | ||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Version 2.x | 1564 | 17 | 2.5MB | 81 ms | 307 ms | 230 ms | 10 sec | 11.912.913 bytes! (11 MB of data) | 0.893 s | 5.8 sec | 8.9 sec | |||||||||||||||||||||||||||||||||||||||
| Version 1.x | 1564 | 17 | 2.5MB | 0.15 sec | 4 sec | 6 sec | 50 sec | 8.5 sec | 0.9 sec | 0. | Records # | Fields # | Data size | Form rendered | Data loaded | Edit entry dialog | Admin UI all records (TableView rendering) | Rendered size (of HTML for admin UI) | All records filtered by one field, no edit controls | All records with sorting (3 fields) with Edit controls | All records, no sorting, no Edit controls | Paged view, 50 records per page sorted, and with edit controls | Paged view, 50 records per page sorted, and no edit controls | Version 2.x | 1564 | 17 | 2.5MB | 81 ms | 307 ms | 230 ms | 10 sec | 11.912.913 bytes! (11 MB of data) | 0.893 s | 5.8 sec | 8.9 sec | Version 1.x | 1564 | 17 | 2.5MB | 0.15 sec | 4 sec | 6 sec | 50 sec | 8.5 sec | 0.9 sec | 0.6 sec |
This tests were executed on a very low-end machine, with 2GB of RAM total, shared VM on SSD, having the PostgreSQL database on the same machine, 1 core, Linux CentOS 7
Updated results for AdminUI loading of 1564 records: ConfiForms version 1.26.2+ (optimizations of edit controls rendering)
...
Please note that the numbers shown above are not reference numbers but just a snapshot of how ConfiForms performs on a very low level hardware. Please also note that the tables it renders are very huge in size and in normal life you will not output something like 1500 records to your users on a page just for fun...
| Info |
|---|
With ConfiForms version 2.x there are no set limits on the number of records. See Where ConfiForms stores data? |
I have a feature request - what shall I do?
...
Each ConfiForms Form is associated with a page (or a blogpost), the page where this form is defined using ConfiForms Form macro container. Administrators for this form are users who: have administrative access to Confluence (Confluence admins and superusers) users who have edit permissions on the page where the form is configured users (users in a group) who are explicitly set to be Form administrators via ConfiForms Form parameter to set additional form admins (they might not have Edit permissions on the page). Also see: Why do I see an extra button with + sign on my form and ownedBy field
Why do I see a "+" button on my form?
This is because you are the administrator of the form and allowed to see some metadata and create records on someones behalf. Ordinal users will not see this button. Also see: Why do I see an extra button with + sign on my form and ownedBy field
What happens with the data stored when the ConfiForms plugin gets disabled/uninstalled
[SERVER/DATA CENTER] Nothing. The data stored with ConfiForms plugin is stored as page metadata and remains in the database even if uninstall the plugin.
ConfiForms plugin is not a replacement for your Jira
[CLOUD] Data will be removed within 2-3 months. You can also request it to be removed earlier if needed
ConfiForms plugin is not a replacement for your Jira
This is very important to understand. ConfiForms is not a replacement to JIRA or any other issue tracking system. However, it could be easily used as one, but keep in mind the dataset size and the complexity of the forms you are building.
...
Another workaround is to type your field reference in some plaintext editor and copy it directly to Confluence editor
ConfiForms is slower to render on Confluence 6.x than on Confluence 5
We have also noticed that - the same plugin code renders slower in Confluence 6 than in Confluence 5. In fact. our macros rendering is not that slower (How to enable logging for ConfiForms add-on), however, the output to user is sent considerably slower than in Confluence 5.
We think, that this might be one of the reasons https://confluence.atlassian.com/confkb/slow-page-rendering-of-large-pages-due-to-http-post-limitations-183137.html
...
Or as follows - type [] then press ctrl+Z and start typing your expression inside the brackets
| Multimedia | ||
|---|---|---|
|
Another workaround suggested by one of our customers
- Type [[]
- And then fill in the expression between the [], removing one extra leading opening bracket
ConfiForms is slower to render on Confluence 6.x than on Confluence 5
We have also noticed that - the same plugin code renders slower in Confluence 6 than in Confluence 5. In fact. our macros rendering is not that slower (How to enable debug logging for ConfiForms app), however, the output to user is sent considerably slower than in Confluence 5.
We think, that this might be one of the reasons https://confluence.atlassian.com/confkb/slow-page-rendering-of-large-pages-due-to-http-post-limitations-183137.html
We have also noticed that rendering times (in fact the time used to sent the rendered output to user) has been improved in Confluence 6.8.x, but is still is slower than on Confluence 5. We are continuing to investigate this issue and looking for solutions.
Why ConfiForms creates a broken page from Confluence template
Why ConfiForms "auto wraps" everything with ConfiForms ListView on a created page
ConfiForms cannot create a Jira issue - I am getting lot's of errors I don't understand
Best tutorial to start with is Creating Jira issue from Confluence with ConfiForms.
Look at the pages mentioned below to learn what your Jira may expect as an input format for a certain field type and how you can prepare the values from ConfiForms to be in the format your Jira expects
| ConfiTemplates Smart Template | ||||||
|---|---|---|---|---|---|---|
| ||||||