Skip Navigation

Generic (but persisting) Form Fields are not available as Notification triggers on Post and User forms

Open

Reported for: Toolset Forms 2.1

Symptoms

Toolset Forms allows you to add Generic Fields to your front-end forms. When you use the (legacy) persist:1 attribute for these fields, the values will be saved to the database.

When using such (persisting) Generic Fields in a form, Toolset Forms Notification options should offer such Generic Fields as triggers for sending notifications.

This is currently not working (since Toolset Forms 2.1 version, released September 3, 2018) and Generic Fields are not available as a trigger for notifications.

Workaround

There is currently no solution to this, other than using native Toolset Types Custom Fields or standard post fields to trigger the notification.

Our Developers are aware of the issue and fix it as soon as possible.

One thought on Generic (but persisting) Form Fields are not available as Notification triggers on Post and User forms

  • Hello, I’m just following up on this issue. The only work around I’ve found is to create custom fields to act as flags. It’s a little cumbersome but it does work.

    Ideally the field that allows you to select an input field to watch would allow me to enter a custom ID or class name, or something else for it to watch and change behavior of the notification based on that.

Leave
a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>