...
| Warning | ||
|---|---|---|
Better solution would be to have a "page/blogpost" field on your form and save the created page id to this field Let's say we have a field of this type called "mypage". In this case to update it with newly created page id you will do something like
|
| Info |
|---|
Important to know that IFTTT macro body is also evaluated as Velocity template (unless this feature is globally switched off by your administrators) - Configuring ConfiForms IFTTT actions#CreatePageactions and rules#CreatePage |
When the new page is to be created the dialog looks like this
...
| Warning |
|---|
This is extremely important when your Confluence template uses layouts! As Confluence is very fragile when the page is having a layout but does not start with a layout tags! |
More on Confluence templates in ConfiForms Using Confluence templates with ConfiForms and avoid configuration duplication
Why ConfiForms "auto-wraps" everything with ConfiForms ListView on a created page
Before ConfiForms IFTTT creates a page it analyzes it's contents to see if you have some macros that need a "view" to work. This macros include: ConfiForms Field, ConfiForms Edit Controls, ConfiForms EntryViewer. But most important is ConfiForms Field macros that are placed alone, not inside the ConfiForms *View macros
When ConfiForms finds this it attempts to "fix" your template (and page) and adds the ConfiForms ListView macro around everything (filtered by current record). So your "viewless" ConfiForms Field macro will work
ConfiForms never auto-wraps the contents if each and every ConfiForms Field macro has been carefully placed inside "views" macros
Make sure you set the filter on the views to
| Code Block |
|---|
id:[entry.id] |
to dynamically show current record's data (this will be processed to have an actual ID, to limit the view to render the data for the current record's data that was used to create the page)
https://wiki.vertuna.com/display/CONFIFORMS/Advanced+integrations+with+IFTTT+macros+with+ConfiForms
...