Conditional visibility not working

Need help
1

Hi everyone,

I have a set of a number of groups on a page, and I want only one at a time to show. Here’s what I’ve done:

All the groups are set to be not visible on page load.

For each group, I have an icon that shows the next or previous group, like this:

image
image1920×1080 207 KB

and then for all of the groups, I have conditional formatting that says none of the other groups are visible when this is not visible, like this:

image
image1920×1080 260 KB

It doesn’t seem to work - the first group shows as it should:

image
image1920×1080 245 KB

but when I click the icon to show the next group, the original group is still displaying as well:

image
image1920×1080 273 KB

Am I doing something wrong here?

2

There may be some slight error in the logic somewhere as this should work, but I would fundamentally change the approach and use a repeating group to hold the text cards.

This would mean that instead of needing lots of complex and not very modular show/hide conditions & workflows, all you’d have to do is have show next/previous on your arrows, and a go to page of rg action on each tab, which should be a lot cleaner.

3

To add to this, maybe even make an option said of your tabs at the bottom and house those in an rg too, that way you’d only need to define the tab action once, and you’d set yourself up to be able to add more cards without changing any workflows.

4

Thank you! For now, I’ve added “hide elements” in the workflows as the order in which people may click on things isn’t sequential. Not the best bit it works. It would be great to find out from someone what is wrong with the conditional formatting…

5

It’s hard to say without looking at the conditional logic of each element and the page in context, but that’s why I would suggest a simpler approach, since currently you’re having to define the same logic six times (5 workflow actions and 5 conditions per element as opposed to 1).

If the tabs at the bottom were an option set wrapped in a repeating group, you could define a single go to page action in a single workflow and send the current tab as a url parameter. This would turn your 5 step conditional logic into a single line, e.g:

Get data from page url is Sea Page 1:this element is visible

So using the above approach, everything will be much easier to organise/modify and you’ll reduce the logic to:

  • 1 workflow with a single go to page action, down from 6 workflows with 5+ actions each
  • A single line visibility condition on each group reading the page parameter, down from 6 elements with 5 conditional steps each. This could also be reduced to a single condition if the you house these groups in an rg too.
6

@ed19 has done justice to the explanation for you @debbie.
If you don’t mind though we can do this together on a call, maybe practical approach will help you better.

1 Like