Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Issues with Confiforms rule logic

Hi, we're having some issues with the logic behind our field definition rules. To troubleshoot this, we created a new basic Confiform with simply a text field and a hidden value. There is also a rule that sets the value of the hidden field if the text field is empty. This is the configuration of the rule:

Untitled.png

Problem is, the condition ALWAYS triggers, no matter the input. This is the form data after our testing:

logic.png

Why is the upper entry also triggering the rule condition? I tried negating the expression to !userinput:[empty] but then it NEVER triggers.

Thankful for any response.

1 answer

1 accepted

1 vote
Answer accepted
Alex Medved _ConfiForms_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Apr 17, 2023

Hi

You have set this rule to trigger on a change in “hiddenvalue” field

Is that what you want? Who changes the value in that field? Do you have some other rule that does that?

Alex

Hi Alex, no we want to track userinput. If userinput is left empty, and only then, we want to set the hidden value to 123.This was one version of all we tried so maybe a bad example to use a screenshot from.

Changing the field name to userinput, or leaving it empty, gives the same result

Alex Medved _ConfiForms_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Apr 18, 2023

So, do you have any reset rules or rules to set other values when the userinput field dis NOT empty?

Here is what happens - as you rule is not set to execute ONLY on the user's action it does execute on form load as well. When the form loads I assume the userinput field is empty by default and this is when the hiddenvalue field get's it's value

Alex

Like Simon Larson likes this

No other rules/reset rules.

That makes a lot of sense. The userinput field is empty by default. Never thought it would trigger on page load. Is there a way to set it up to trigger only once you submit the form?

Alex Medved _ConfiForms_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Apr 20, 2023

Yes, of course - set it to "Execute only on user action".

But in your case I would implement an IFTTT macro to update the field if the userinput is empty

So it will run on "post submit"

Like Simon Larson likes this

Will try this, thank you Alex

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events