You are viewing limited content. For full access, please sign in.



Feature Request: Field Rule Condition of Has Changed

asked on August 7, 2023

I like the new field rules capabilities more and more each day. Thank you for all the work that has been put into them.

With that being said, I have found a new feature that would be really useful. This time it is with the condition options. I would like to be able to set a condition based on whether the value of a field has changed or not changed from the initial value when the form is loaded for the end user.

For example, I have a process where at step 1 the end user sets the value of a field to determine who it goes to at step 2. When the instance goes to step 2 there are field rules that get applied for specific fields to be disabled, required, etc., but of course sometimes the user at step 1 selects the wrong person for the instance to go to, so they need to change it. If they change that one field, I do not want the required fields to take effect, either by creating a field rule to do that or by hiding them.

4 0


replied on August 8, 2023

There are so many times where a "field has changed" field rule could be useful!

3 0
replied on August 8, 2023

This is a great idea, and it might not be all that hard to implement since the dataset variables already use the "current" server-side values so maybe just a matter of providing access to them.

I think providing access to "dataset" values for field rules would be great, but why stop there when you could also make them available for use in other areas like the LFForm object.

Technically, you could probably accomplish something similar using hidden fields that are set to use the dataset values as the default, but then you have to add a bunch of extra fields.

2 0
You are not allowed to follow up in this post.

Sign in to reply to this post.