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


See also Known issues

Development versions could be found here: http://vertuna.com/builds/

Known issues

Published versions and changes

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

Version 3.4.6

Version 3.4.5

Version 3.4.4

Version 3.4.3

Version 3.4.2

Version 3.4.1

Version 3.4.0

Version 3.3.9

Version 3.3.8

Version 3.3.7

Version 3.3.6

Version 3.3.5

Version 3.3.4

Version 3.3.3

Version 3.3.2

Version 3.3.1

Version 3.3.0

Version 3.2.3

Version 3.2.2

Version 3.2.1

Version 3.2.0

Version 3.1.2

Version 3.1.1

Version 3.1.0

Version 3.0.8

Version 3.0.7

Version 3.0.6

Version 3.0.5

Version 3.0.4

Version 3.0.3

Version 3.0.2

Version 3.0.1

Version 3.0.0

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


Version 2.28.4

Version 2.28.3

Version 2.28.2

Version 2.28.1

Version 2.28.0

Version 2.27.30

Version 2.27.29

Version 2.27.28

Version 2.27.27

Version 2.27.26

Version 2.27.25

Version 2.27.24

Version 2.27.23

Version 2.27.22

Version 2.27.21

Version 2.27.20

Version 2.27.19

Version 2.27.18

Version 2.27.17

Version 2.27.16

Version 2.27.15

Version 2.27.14

Version 2.27.13

Version 2.27.12

Version 2.27.11

Version 2.27.10

Version 2.27.9

Version 2.27.8

Version 2.27.7

Version 2.27.6

Version 2.27.5

Version 2.27.4

Version 2.27.3

Version 2.27.2

Version 2.27.1

Version 2.27

Version 2.26.6

Version 2.26.5

Version 2.26.4

Version 2.26.3

Version 2.26.2

Version 2.26.1

Version 2.26

Version 2.25.7

Version 2.25.6

Version 2.25.5

Version 2.25.4

Version 2.25.3

Version 2.25.2

Version 2.25.1

Version 2.25

Version 2.24.7

Version 2.24.6

Version 2.24.3

Version 2.24.2

Version 2.24.1

Version 2.24

Version 2.23.1

Version 2.23

Version 2.22

Version 2.21.6

Version 2.21.5

Version 2.21.4

Version 2.21.3

Version 2.21.2

Version 2.21.1

loader constraint violation: when resolving method 'void javax.mail.internet.MimeBodyPart.setDataHandler(javax.activation.DataHandler)' the class loader

Version 2.21.0

Version 2.20.5

Version 2.20.4

Version 2.20.3

Version 2.20.2

Version 2.20.1

Version 2.20

Version 2.19.5

Version 2.19.4

Version 2.19.3

Version 2.19.2

Version 2.19.1

Version 2.19

Version 2.18.16

Version 2.18.15

Version 2.18.14 

Version 2.18.13

Version 2.18.12

Version 2.18.11

Version 2.18.10

Version 2.18.9

Version 2.18.8

Version 2.18.7

Version 2.18.6 

Version 2.18.5

Version 2.18.4

Version 2.18.3

Version 2.18.1

Version 2.18

Version 2.17.1

Version 2.17

Version 2.16.10

Version 2.16.9

Version 2.16.8

Version 2.16.7

Version 2.16.6

Version 2.16.5

Version 2.16.2

Version 2.16.1

Version 2.16

[entry.date.startDate.timestamp.add([entry.periodicy.multiply(86400000)])]-[entry.date.endDate.timestamp.add([entry.periodicy.multiply(86400000)])]

Version 2.15.8

Version 2.15.7

Version 2.15.6

Version 2.15.5

Version 2.15.4

Version 2.15.3

Version 2.15.2

Version 2.15.1

Version 2.15

Version 2.14.4

Version 2.14.3

Version 2.14.2

Version 2.14.1

Version 2.14

Version 2.13.9

Version 2.13.8

Version 2.13.7

Version 2.13.6

Version 2.13.5

Version 2.13.4

Version 2.13.3

Version 2.13.2

Version 2.13.1

Version 2.13

Version 2.12.4

Version 2.12.3

Version 2.12.2

Version 2.12.1

Version 2.12

For discovery service documentation

/ajax/confiforms/rest/jira-issue-mapping.action

Examples:

For web service connection

/ajax/confiforms/rest/jira-issue-mapping.action?webServiceId=a4c253e1cc9d7534f136279e03de444d&projectKey=JTEST&issueType=Story

For applink

/ajax/confiforms/rest/jira-issue-mapping.action?applinkName=MyJira&projectKey=JTEST&issueType=Task
"fields": {
   "field1":"field value",
   "field2": "2020-04-25"
}

Version 2.11.2

Version 2.11.1

Version 2.11

Version 2.10.15 

Version 2.10.14

Version 2.10.13

Version 2.10.12

Version 2.10.11

Version 2.10.10

Version 2.10.9

Version 2.10.8

http://YOUR-CONFLUENCE-SERVER/ajax/confiforms/rest/create-page-with-view.action?pageId=<PAGE_ID>&formName=<FORM_NAME>&viewType=form-view

pageId - where the form is located
formName - name of the form
viewType - type of view to create (list-view, card-view, table-view, form-view, plain-view, clean-view)

Optional parameter:
withLabel - true or false, to tell the service to render the field with a label
parentPageId - custom page to use as parent page (by default the page is created under the page were the ConfiForms form is)

Version 2.10.7

Version 2.10.6

Version 2.10.5

Version 2.10.4

Version 2.10.3

Version 2.10.2

Version 2.10.1

Version 2.10

Version 2.9.6

Version 2.9.5

Version 2.9.4

Version 2.9.3

Version 2.9.2

Version 2.9.1

Version 2.9.0


function onCFBeforePrint(content) {
}


You can override it for example like this

onCFBeforePrint = function(content) {
   alert('The form is about to be printed with the following contents: ' + content.html());
}


Version 2.8.3

Helps you to see what version of the attachment is used by ConfiForms record, what page is referenced and it's internal IDs and attributes

/ajax/confiforms/rest/storage-details.action?pageId=819201&formName=f&fieldName=mypage

- pageId: where the form is defined
- formName: name of the form
- fieldName: (optional) to limit the output to analyze only the specific field and it's data

Option needs to be enabled in the app's general settings first and then can be accessed from any form's Admin UI



Version 2.8.2

Version 2.8.1

Version 2.8.0

Version 2.7.5

Version 2.7.4

Version 2.7.3

Version 2.7.2

Remember that you need to allow export and search on your ConfiForms Form (Definition) and you form shall not be set to shown only own records to non-admin users. Also you shall have ConfiForms views built over your form. As Confluence search index is disconnected from ConfiForms data then you need to make sure you inform Confluence about the need to reindex the contents - This can be done with the help of ConfiForms IFTTT Integration Rules macro with action set to "Force page to reindex". Please be aware that this action only suggests Confluence indexer to index the page, and actual indexing might take a while to start and complete

Version 2.7.1 

Version 2.7.0

Version 2.6.1

Version 2.6.0

Version 2.5.2

Version 2.5.1

Version 2.5.0

Version 2.4.1

Version 2.4.0

Version 2.3.2

Version 2.3.1

Version 2.3.0

Version 2.2.3

Version 2.2.2

Version 2.2.1

Version 2.2.0

Version 2.1.2

Version 2.1.1

Version 2.1.0

Version 2.0.38

Version 2.0.37

@ExportAsService({ConfiFormsStorageComponent.class})
@Named("confiFormsStorageComponent")
public interface ConfiFormsStorageComponent {

  String findFieldValueById(ContentEntityObject contentEntityObject, String formName, String id, String fieldName);

  RegEntry findById(ContentEntityObject contentEntityObject, String formName, String id);

  List<RegEntry> findByAll(ContentEntityObject contentEntityObject, String formName);

  List<RegEntry> findRecordsByCurrentUser(ContentEntityObject contentEntityObject, String formName);

  List<RegEntry> findRecordsByUser(ContentEntityObject contentEntityObject, String formName, String username);

  void updateField(ContentEntityObject contentEntityObject, String formName, String query, String field, String value) throws Exception;
}

Version 2.0.36

Version 2.0.35

Version 2.0.34


Version 2.0.33

Version 2.0.32 

Version 2.0.31

Version 2.0.30

Version 2.0.29

Version 2.0.28

Version 2.0.27

Version 2.0.26

Version 2.0.25

Version 2.0.24

Version 2.0.23 

Version 2.0.22

Version 2.0.21

Version 2.0.20

Version 2.0.19


Version 2.0.18

Version 2.0.17

Version 2.0.16

<ac:structured-macro ac:macro-id="d860f6a8-91e0-4b60-ac8b-f9d77f53aa33" ac:name="confiform-table" ac:schema-version="1">
  <ac:parameter ac:name="formName">f</ac:parameter>
  <ac:rich-text-body>
    <p>
      <br/>
    </p>
  </ac:rich-text-body>
</ac:structured-macro>
<p>only equals</p>
<ac:structured-macro ac:macro-id="bcc29516-fa5c-46db-8a0a-4ff1248285e0" ac:name="confiform-table" ac:schema-version="1">
  <ac:parameter ac:name="filter">a1:[entry._func.asEntryRef(entry.a2)]</ac:parameter>
  <ac:parameter ac:name="formName">f</ac:parameter>
  <ac:rich-text-body>
    <p>
      <br/>
    </p>
  </ac:rich-text-body>
</ac:structured-macro>

Version 2.0.15


Version 2.0.14

Version 2.0.13

Version 2.0.12

Version 2.0.11

Version 2.0.10

Version 2.0.9

Version 2.0.8

Version 2.0.7

Version 2.0.6

Version 2.0.5

Version 2.0.4


Version 2.0.3

Version 2.0.2

Version 2.0.1