Easy Forms 1.11.0

Optimized Memory Usage for Blog Post Form Reporting

This release contains a change that decreases the memory usage for the logic used in Easy Form Report macros to find an Easy Form that is in a Blog Post.

This change has been made for our efforts to improve Easy Forms in every way we can to maximize scalability for large Data Center deployments.

The most common use-case is for an Easy Form to exist on a Page, not a Blog Post, and this change does not affect that majority use-case. However, it does affect the minor use-case of reporting on an Easy Form that is on a Blog Post.

It is a Breaking Change

Easy Form Report macros that are reporting on an Easy Form that is in a Blog Post will need to be edited and saved to work with this change. The edit will consist of re-typing the same Blog Post title into the “Page with form” input, select the same form name in the “Form name” input, and save the macro.

Doing this edit/save will change the “Page with form” parameter so that it contains the title of the Blog Post in Confluence’s format for date paths for blogs. This format that includes the posting date in addition to the Blog Post title, like “/2020/09/21/My Blog Post”. The order of the date in Confluence’s format is year, month, date (ISO-8601 order).

An Easy Form Report macro that is hooked up to Easy Form that is in a Blog Post will not be able to find the Easy Form immediately after upgrading to version 1.11.0. You will see an error message for such Easy Form Report macros:

How to Find Blog Posts Containing Easy Form Reports

To find the Easy Form Report macros that you will edit, you need to find all Blog Posts that contain Easy Form Report macros.

You can use Confluence’s advanced search to find all blog posts that contain an Easy Form Report macro. Do an advanced search like this:

type:blogpost AND macroName:easy-form-report

See https://confluence.atlassian.com/doc/confluence-search-syntax-158720.html#ConfluenceSearchSyntax-SearchspecificfieldsinConfluence

How to Edit the Easy Form Report Macro to Fix it

  • This is ONLY necessary for an Easy Form Report that is hooked up to an Easy Form that is in a Blog Post

  • Edit the “Page with form” parameter to set it to the same title:

  • As you type the Blog Post title into the input the selector will automatically populate. Choose the same Blog Post title you had before:

  • The change in the “Page with form” input will change the format from a simple title to a title that is prefixed by the date of the posting. It also triggers the “Form name” input to automatically populate with the names of the Easy Form macros that are in that Blog Post. Select the same “Form name” that you had originally set:

  • Save the macro, publish the page, and you can now use the Easy Form Report

 

Related Documentation

https://appfire.atlassian.net/wiki/spaces/SUP/pages/147360382

https://appfire.atlassian.net/wiki/spaces/SUP/pages/147358680