Question

Unusual Behavior Collection with Field Rules

Forms Version 11 Business Processes Feature How To

Updated January 9, 2023

asked on April 26, 2022

I'm creating a form for field staff to input their availability for the upcoming month. I have a radio button variable "Position" with 4 options: "Part Time", "Student Cohort", "Weekend Float", and "PRN".

There is also a collection variable "Availability". Two of the variables are a checkbox "PTO" and a radio button with the options "PTO" and "Clinical".

The desired outcome is for the "PTO" checkbox to show when "Part Time", "Weekend Float", or "PRN" is selected and the radio button when "Student Cohort" is selected.

The problem I am running into is that the field rule is only triggered for the first row of the collection. The checkbox and radio button both show on rows added after the "Position" is selected.

Picture of problem:

Picture of field rules:

This is on prem v11 forms. I'm unsure if I have something set up incorrectly and would appreciate assistance with getting the desired outcome on this form.

0 0

Answer

SELECTED ANSWER

replied on April 27, 2022

Hi Carlos,

It is a bug, the field rule is not triggered after add new set. The current workaround is after you add new set of collection, you need to select the radio button option again to trigger the field rule. We have fixed it internally, the fix will be released with next update of Forms.

0 0

View 1 previous reply

replied on August 27, 2022 • Show version history

Hi @████████

I think I've found a variation of this bug. Can you confirm if you can reproduce it?

Using the modern forms designer, on premise, 11.0.2201.20436.

Collection:

- Drop Down #1, Options: Yes/No, Default: Yes

- Drop Down #2, Options: Yes/No, Default: Yes

- Section #1

-- 6 x Number/Currency Fields, Default (Non-Zero) Values are set.

- Section #2

-- 6 x Number/Currency Fields, Default (Non-Zero) Values are set.

Field Rules:

If Drop Down #1 = Yes, Show Section #1. Do not save if hidden.

If Drop Down #2 = Yes, Show Section #2. Do not save if hidden.

(Effectively, you can have four combinations - Yes/Yes, No/No, Yes/No, No/Yes)

Recreating the problem:

By default, one collection will show, and the defaults are Yes/Yes, so both sections 1 & 2 are shown. Output from a submission with a single collection row is correct, and values from fields within each section of the collection row are saved on submission. (Working as expected)

If you add a second collection, and do not adjust the section rules from default state (Yes/Yes), the values from within the sections will save correctly for each collection row upon submission. (Working as expected)

However, if at any collection row, you have a Yes/No, or No/Yes configuration, which triggers the rule to hide a section, the form collection correctly displays the preference per row HOWEVER, upon submission, data for all rows is stored differently to what was set at the collection row level. (Not working as expected)

This results in blank/null values being stored for the fields contained within one or both the sections controlled by rules - and it applies to all collection rows. So if the first row was Yes/No, then Section #2 for all rows is set to null - regardless of the subsequent collection rows being set being Yes/Yes (and displaying correctly in the front end).

If you could test that the above issue is fixed on the forthcoming bug fix release, that would be appreciated. Unfortunately this weird bug has cost us many hours of troubleshooting and more specifically, in refactoring our approach as it dramatically impacts the user experience.

Thanks!

0 0

replied on September 5, 2022

Hi Kris,

I am sorry this bug wasted your time. I can reproduce the issue you reported, it is related to using field rule to hide section inside collection, the bug is logged as 394108, we will fix it in the coming release.

1 0

replied on January 9, 2023 • Show version history

The related bugs have been fixed with Forms 11 Update 3.

New rows or sets added now follow the field rule when the criteria field is outside the collection or table and the target field is inside the collection or table. (371183)

Rules no longer ignore all the field values for all the sets when in one set the section is hidden. (394108)

You can see other changes of Forms 11 Update 3 from https://support.laserfiche.com/kb/1014413/list-of-changes-for-laserfiche-forms-11-update-3 and get Forms 11 Update 3 from Laserfiche 11 package https://support.laserfiche.com/kb/1014263/software-versions-and-fixes-included-in-the-laserfiche-11-download-package.

0 0

Replies

replied on November 14, 2022

We have an occurrence of similar bug where the field rule is not fired for a radio button but it is only the second radio button and not others.

0 0

View 2 previous replies

replied on November 15, 2022

Can you provide more details for the bug you ran into so that we can confirm it has been fixed? For example, show us how the field rule is configured and show us what doesn't work with screenshots or videos.

0 0

replied on November 15, 2022

0 0

replied on November 15, 2022

Rule 8 does not allow the form image to be displayed correctly and the radio button Environmental Design selection does not show in the form image.

screencapture-sbo-lfforms-sd35-bc-ca-Forms-moderndesign-313-2022-11-15-09_45_43.png (219.08 KB)

| Download

0 0

replied on November 15, 2022

This shows the form image saved to the repository.

0 0

replied on November 15, 2022 • Show version history

As a result of this bug, I have stopped using the new form design and will stick with Classic. I have rebuilt the form using Classic and it shows no problems.

The form is longer than shown above. There is a section shown for each of the radio buttons.

0 0

You are not allowed to follow up in this post.

Question

Question

Unusual Behavior Collection with Field Rules

Answer

Replies

Sign in to reply to this post.