nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Confiforms: Define a form on one page but show results only from submitting pages

Katherine Barako

Hello,

I have a workflow where pages are created from created pages in a chain. I would like to keep my form definitions in a centralized location instead of re-defining them on each created page.

I am looking to define a form "data" on Page A, which creates Pages B and C. I would like pages B and C to have registration buttons and tableviews for "data" on Pages B and C. However, I want the table in B to only show the data submitted from Page B, and the table in C to only show the data submitted from Page C.

I'm very new to confluence and not sure of the right way to approach this. I tried putting id:[entry.id] in the entries dataset filter for the tableview, which didn't work. I stuck an autopage field in and tried autopage:[entry.autopage], but that didn't seem to work either.

Could someone please point me in the right direction? Thanks very much.

Accepted answers

Alex Medved _ConfiForms_

Hi @Katherine Barako

What you are asking is really what ConfiForms is all about - you configure the form once and use it in different places, as you like and need - even with custom designs and layouts if that's desired

So, what is not working for you with the "centralized" approach?

Page B and C are using the form from a page A?

Then the simplest way to filter the data per page would be to use an autopage field and use it in filtering agains the "current page"

autopage:[entry._page]

https://wiki.vertuna.com/spaces/CONFIFORMS/pages/5341277/Accessing+field+values+and+properties#Accessingfieldvaluesandproperties-Additionalvaluesavailableinthecontext

Alex

All comments

Tomislav Tobijas

Hey @Katherine Barako ,

Alex from Vertuna (vendor) might jump on here as well to provide some assistance, but you could also reach out to the product/vendor team directly via one of the following channels. 👈

Marketplace teams are usually quite responsive and helpful when it comes to their apps, so I would probably suggest going in that direction.

I haven't used ConfiForms that much to be able to answer this 😕

Cheers,
Tobi

Alex Medved _ConfiForms_

Hi @Katherine Barako

What you are asking is really what ConfiForms is all about - you configure the form once and use it in different places, as you like and need - even with custom designs and layouts if that's desired

So, what is not working for you with the "centralized" approach?

Page B and C are using the form from a page A?

Then the simplest way to filter the data per page would be to use an autopage field and use it in filtering agains the "current page"

autopage:[entry._page]

https://wiki.vertuna.com/spaces/CONFIFORMS/pages/5341277/Accessing+field+values+and+properties#Accessingfieldvaluesandproperties-Additionalvaluesavailableinthecontext

Alex

Katherine Barako

Thank you!! Yes! I got it working.

Katherine Barako

@Alex Medved _ConfiForms_ I thought I had it working for a while but I'm actually having an issue now where "autopage" is recording the page the form definition sits on instead of the page the form registration is being clicked on. As a result, when it's comparing autopage to the current page, nothing is showing up on the filter.

Do you know how I can fix this?

Alex Medved _ConfiForms_

Sorry, I dont think I understand

autopage field records the page where the registrations control field is placed or where you have edited the record (in case if the field is set to track that as well)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

data-center

addon-com.vertuna.confluence.plugins.confiforms

confiforms

confluence-data-center