Child pages
  • Using ConfiForms LiveView macro

This is the documentation for ConfiForms Server/Data Center app

However, this might also work for ConfiForms cloud and in most cases it does. But please see this page to understand the differences between server and cloud versions of the ConfiForms app.

Please note that this macro is still in BETA version. Feedback is very welcome (please use the "Get Support" button)

ConfiForms LiveView macro helps you to build reusable and easy to modify layouts. It is not only about the ConfiForms, but any layouts that you want to build and make the dynamically updatable without a need to update every other page that might be using this layout

Configuration

Type in the page editor {Live

to get the ConfiForms LiveView macro suggested to you

The macro has very few parameters that are easy to follow and understand

You have to choose the page the this macro will use as a template and render for your users

You can make it hidden if necessary.

You can make it take the request parameters as an input to be send to your page (which this macro renders). Macro takes parameters from page properties automatically and this is the recommended method to configure it

You can make it to load asynchronously - not blocking the page rendering, but after the page is refreshed/loaded - makes things more responsive to your users

And also supports caching, to make things to render even faster (when realtime data is not really required and cached data is more than fine to have)

Example

Let's say the page that we have and want to use as a template expects a variable under the name "director"

We can have something like this on our page.

This way the value "alexm" will be assigned to variable "director"

And let's assume that the template page is very simple and uses it in the filtering expression in one of it's ConfiForms views (TableView in this case)

Something like this

This is how you can reference this parameter 


director:${director}

When the page is rendered through the LiveView macro the value for the ${director} variable will be taken from the page properties and will be alexm

Alternatively, the director variable can be referenced as [page_property.director]




  • No labels