This is the documentation for ConfiForms CLOUD app
Introduction of a new editor for Confluence cloud by Atlassian has made the configuration of ConfiForms much harder to do and is more limited. Especially when it comes to designing custom layouts for your forms.
The new editor just does not support nesting the bodied macros and that makes the custom layouts very hard to do and limits you a lot.
Here is what you need to know when configuring ConfiForms in Confluence new editor
|Macro / functionality||Remarks|
|ConfiForms IFTTT macros are bodied macros and usually are put inside the ConfiForms Form Definition macro (as they belong to the form and define it's behaviour)|
|ConfiForms Registrations Control / FormView macro is a bodied macro and cannot be placed inside the ConfiForms Form Definition macro|
Place it outside and set the form name to point at your form. Also you can easily put this macro on a separate page if necessary. To decouple you form configuration and form presentation.
You still can have custom layouts for your form, but you need to be aware that you will not be able to put bodied macros inside this macro
|General: All ConfiForms views macros are bodied macros and therefore cannot be put as a source to other macros|
|Lots of macros are missing, including the "No Format" used in the tutorials|
Yes, Atlassian has decided to remove lots of macros and we suggest to use "Code" macro as a workaround when "No Format" is mentioned in tutorials
|Very limited possibilities to customize form layouts (ConfiForms Registrations / FormView macro) and pages created with ConfiForms (via ConfiForms IFTTT macros)|
Unfortunately new editor for Confluence cloud sets lots of limitations and reduces lots of possibilities in layout customization. See the tickets referenced in other rows from this table and some more below
For ConfiForms IFTTT macros (for creating the pages in Confluence) this is somewhat dramatic - as ConfiForms IFTTT macro itself is a bodied macro and new editor lacks the support for nesting bodied macros you get a very very limited possibilities.
One workaround we advise to do is to use Confluence templates for the pages you create with ConfiForms and reference them instead of defining the page layouts within the ConfiForms IFTTT macro