The conditional rules description reads List values, one per line, that will trigger this action. If you leave this blank, this component will always display.

When defining components the descriptions read Key-value pairs MUST be specified as "safe_key|Some readable option"

The wording Key-value suggests that the text after the pipe | is the value. Conditional rules requires you to enter keys not values.

We should standardise these descriptions across the board.

Comments

quicksketch’s picture

quicksketch
he/him
commented

Yep I agree. Really we could use a much better interface for specifying conditional elements so users don't need to know the keys of select elements at all.

jimtobias’s picture

jimtobias commented
Version: 7.x-3.x-dev » 6.x-3.11
Category: feature » support

Just to be clear, you're saying that we have to enter the keys, not the values, into the conditional rules? So if it's:

A|Always
B|Sometimes
C|Never

We put in A, not Always.

BTW, is there a definition of a 'safe_key' anywhere?

mhurston’s picture

mhurston commented

I would like to know this too. I have tried entering the following with no luck.

Question 1: Select A, B or C

Question 2: *

* Only appears if you answered A

I select "Is one of" and then tried:
A | Always, A, Always - all just hid the question regardless of what was chosen.

quicksketch’s picture

quicksketch
he/him
commented
Status: Active » Closed (fixed)

This is being addressed in #1215456: Multiple and same-page conditional rules, though it's looking like this will be moved into the D7-only 4.x version.