...

• (Smart) multi row field - new field type to help with "inline" creation of master-details structures
• "ConfiQuery" field type to help you to link other form's data and associate it with a particular field/row in your current form
• New ConfiForms IFTTT Action to Audit records
• New ConfiForms IFTTT action Rename attachment 

Version 2.0.12

• Optimized logic for retrieving field's properties. Our tests show the rendering performance has been improved 50-75%, in some cases 100%. Affects all the "views" macros, as well as filters and sorting
• Fixed issue with import API for importing users list into user's multi-select field
• Fixed issue with escaping the HTML input while generating the email message with IFTTT, which has caused problems with later parsing and including attachments properly

• Support for wildcards (*) in navigation instructions when applying it on a JSON input. A wildcard means the first property in JSON will be taken 

  Why? Consider this JSON example. Property values can easily change here, but the structure itself is preserved
  
  

  Code Block
  { "return": [ { "somehostname01": { "file_|-/etc/ssh/sshd_config_|-/etc/ssh/sshd_config_|-managed": { "comment": "File /etc/ssh/sshd_config is in the correct state", "pchanges": { }, "name": "/etc/ssh/sshd_config", "start_time": "11:01:54.394381", "result": true, "duration": 21.685, "__run_num__": 0, "__sls__": "abb.sshd", "changes": { }, "__id__": "/etc/ssh/sshd_config" } } } ] }

  Here is how you can take the "comment" field value

  Code Block
  j.asJSON.return.*.*.comment

  which reads to, take the value of a "j" field, transform it to JSON, then get the first property value, then get the first property of a returned value and then lookup for the "comment" property value

  
  

• Support for "cf_force" parameter in URLs while creating filtered views. See more: Creating links to filter views from request parameters - url
• Officially approved by Atlassian version for Data Center!
• As per request from Atlassian we now set the default limits on the number of records rendered by ConfiForms views. The default is 500 records, you can change it in macro properties parameters or set to "NO LIMIT". 
• Fixed issue with emails generated by IFTTT where file holding fields were used to show the other properties of the file (were not visible on rendered email, which is now fixed)
• Fixed issue with incorrect escaping of the data while importing with Import API
  
  

Version 2.0.11

• Fixed issue with removing attachments when a record with file/attachment field get's deleted
• Fixed issue with storage auto-migration from ConfiForms version 1 to version 2 when content is re-indexed (which has caused issues due to read-only transactions used by the indexer)
• Fixed issue with null pointer exception thrown when IFTTT was processing onDeleted events and IFTTT actions were using ConfiForms Field macros (sending email on when a record gets deleted, etc)
• Implemented support for READ-ONLY mode in Confluence. ConfiForms becomes READ-ONLY as well.

...