Contrib.social

Email Handler - Conditional Logic - Table Select field - condition disregarded

Open on Drupal.org →
Created on 3 December 2024, 11 months ago

Problem/Motivation

A "Conditional Logic" in an "Email Handler" based on a "Table Select" field is not working. Even if the condition is not satisfied, the email is still sent.

Steps to reproduce

  1. Create a webfrom
  2. Add a field of type "Table Select"
  3. Add options to this field (two or more)
  4. Go to Settings > Email Handler and edit the settings of either Notification or Confirmation
  5. Change the body so you can see the "Table Select" field in the email that arrives to you (so you can confirm that is was checked or unchecked)
  6. Change the recipient so the email is sent to you (in case the default for your site is not yourself)
  7. Under "Conditions", create a condition like this:
    • State: (Enabled or Disabled)
    • Element: All
    • Pick one of the "Table Select" field options
    • Trigger/Value: (Checked or Unchecked)
  8. Save your changes and run some tests, with that "Table Select" field option checked and unchecked.

I tried different combinations of "State" and "Trigger/Value" but for all combinations the emails were sent.
I'm guessing that because I have a single condition, the "Element" field option (All/Any/One) defaults to "All".
I've tested the conditional logic with conditions based on text fields (filled/unfilled) and those worked as expected.

Am I missing something? Is there an extra step or module or something else I need to do in order to use "Table Select" fields as conditional logic for email handlers?

FYI, I'm on Drupal 10.3.10 (staging) and 10.3.9 (production). The result is the same on both.

Thanks,
Alex

🐛 Bug report
Status

Active

Version

6.3

Component

Code

Created by

🇨🇦Canada aarantes

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @aarantes
  • Comment 10 months ago →
    🇺🇸United States jrockowitz Brooklyn, NY

    The attached webform is replicating the issue.

  • Comment about 2 months ago →
    🇺🇸United States thumy

    I encountered the same issue (which is how I stumbled on your post) and eventually figured out how to make it work! Instead of using the checked/unchecked trigger, I had to choose the "Value is" (or "Value is not") trigger and enter the option value for that checkbox. I hope that helps!

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024