Date: Tue, 19 Mar 2024 09:53:28 +0200 (EET) Message-ID: <904820637.329.1710834808164@wiki.vertuna.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_328_113530352.1710834808030" ------=_Part_328_113530352.1710834808030 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Simple, but powerful concept to show how template names can be dynamical= ly looked up from field values and used to create pages
Since some time ago we have added support to reference Confluence templa= tes from ConfiForms IFTTT's and from ConfiForms Registration Control macros= .
This enables you to avoid content duplication and reuse the content / la= yout.
Templates can be referenced using
See more about this on Using ConfiForms = app as template engine to create pages in Confluence and Using Confluence templates with ConfiForms and= avoid configuration duplication
In version 1.19 of ConfiForms app we have added a way to dynamically set= the name of the template you want to use:
[templa= te.[entry.somefield]]
Assuming you have a dropdown field or a text field called "somefield" wh= ere a user can choose or specify the template to use when a page is to be c= reated (with IFTTT for example)
This way we can easily create, with the same IFTTT, pages with different= layouts
FROM VERSIO= N 1.47.2
You can include the template without evaluating it's parameters<= /strong>.
[rawtem= plate.[entry.somefield]]
The contents of the template (value for template name will be taken from= "somefield") will not be evaluated against the current record, but will be= included as-is