Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Macro / functionalityRemarks
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

Jira
serverAtlassian JIRA
serverId144880e9-a353-312f-9412-ed028e8166fa
keyCONFCLOUD-68323

Jira
serverAtlassian JIRA
serverId144880e9-a353-312f-9412-ed028e8166fa
keyCONFCLOUD-69962

Jira
serverAtlassian JIRA
serverId144880e9-a353-312f-9412-ed028e8166fa
keyCONFCLOUD-66769

Jira
serverAtlassian JIRA
serverId144880e9-a353-312f-9412-ed028e8166fa
keyCONFCLOUD-70237

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

Jira
serverAtlassian JIRA
serverId144880e9-a353-312f-9412-ed028e8166fa
keyCONFCLOUD-68323

Jira
serverAtlassian JIRA
serverId144880e9-a353-312f-9412-ed028e8166fa
keyCONFCLOUD-58656

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

Jira
serverAtlassian JIRA
serverId144880e9-a353-312f-9412-ed028e8166fa
keyCONFCLOUD-66888

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

Jira
serverAtlassian JIRA
serverId144880e9-a353-312f-9412-ed028e8166fa
keyCONFCLOUD-67825

Jira
serverAtlassian JIRA
serverId144880e9-a353-312f-9412-ed028e8166fa
keyCONFCLOUD-65774

Jira
serverAtlassian JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId144880e9-a353-312f-9412-ed028e8166fa
keyCONFCLOUD-66752

https://confluence.atlassian.com/confcloud/we-re-cleaning-up-the-macro-browser-946028471.html

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

Jira
serverAtlassian JIRA
serverId144880e9-a353-312f-9412-ed028e8166fa
keyCONFCLOUD-67825

Jira
serverAtlassian JIRA
serverId144880e9-a353-312f-9412-ed028e8166fa
keyCONFCLOUD-65640

Jira
serverAtlassian JIRA
serverId144880e9-a353-312f-9412-ed028e8166fa
keyCONFCLOUD-66752

Jira
serverAtlassian JIRA
serverId144880e9-a353-312f-9412-ed028e8166fa
keyCONFCLOUD-58656

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

Macro preview is not available

This is blocked by issues (even marked as "fixed" issues are not really fixed (sad))

Jira
serverAtlassian JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId144880e9-a353-312f-9412-ed028e8166fa
keyCONFCLOUD-64923

Jira
serverAtlassian JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId144880e9-a353-312f-9412-ed028e8166fa
keyCONFCLOUD-69962

Jira
serverAtlassian JIRA
serverId144880e9-a353-312f-9412-ed028e8166fa
keyCONFCLOUD-66858

Performance issues

This affects us in a way that when a static macro, such as DataView in ConfiForms, is rendered on a page we get 2 identical concurrent calls to our backend to render an output... instead of just one

Jira
serverAtlassian JIRA
serverId144880e9-a353-312f-9412-ed028e8166fa
keyCONFCLOUD-69108

Jira
serverAtlassian JIRA
serverId144880e9-a353-312f-9412-ed028e8166fa
keyCONFCLOUD-72517

Jira
serverAtlassian JIRA
serverId144880e9-a353-312f-9412-ed028e8166fa
keyCONFCLOUD-72518

Jira
serverAtlassian JIRA
serverId144880e9-a353-312f-9412-ed028e8166fa
keyCONFCLOUD-72519

Jira
serverAtlassian JIRA
serverId144880e9-a353-312f-9412-ed028e8166fa
keyCONFCLOUD-72520

Jira
serverAtlassian JIRA
serverId144880e9-a353-312f-9412-ed028e8166fa
keyCONFCLOUD-72521

Jira
serverAtlassian JIRA
serverId144880e9-a353-312f-9412-ed028e8166fa
keyCONFCLOUD-72522

Copy/paste from a legacy editor (or from server/dc editor) into a new Confluence (aka "fabric") editor

Info

Copying and pasting from legacy editor to legacy editor works without any issues - for cloud and for server/dc. Which is awesome and how it should be with new editor...

Jira
serverAtlassian JIRA
serverId144880e9-a353-312f-9412-ed028e8166fa
keyCONFCLOUD-69195