...
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) | In the new editor you cannot do that and have to place ConfiForms IFTTT macros outside the ConfiForms Form Definition macro and you need to link the rules and the form via the "Form name" parameter
| ||||||||||||||||
| 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 | Creating charts and graphs, filtering the tables with other plugins is impossible in Confluence cloud due to limitations of this platform and the new editor in particular
| ||||||||||||||||
| 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
https://confluence.atlassian.com/confcloud/we-re-cleaning-up-the-macro-browser-946028471.html |
