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

Question

Question

New forms designer field rules when saving

Forms Version 11
Updated February 14, 2023
asked on December 27, 2022

I'm pretty excited about the new Forms Designer for on-prem. Something I just noticed while trying to convert a process from the old to new designer is that the saved version of the form doesn't seem to respect field rules. I have some things set to always hide that are, in fact, showing up on the saved form. I also have some things that are a little more dynamic (show a warning if two fields don't match) that also are not being evaluated upon save.

Is this a known issue? Will it be fixed?

0 0

Replies

replied on December 27, 2022

You also have to be careful converting a Classic form that has hidden fields that are hidden using the CSS Class 'hidden'. You can't unhide them in the design view as they are not visible.

Plus, I have not been able to figure out how to get the JavaScript to work in the Modern Designer yet. 

0 0
replied on January 4, 2023

We are aware of the hidden CSS class issue, the workaround is add ".pdc.hidden { display: block; }" in CSS section for the form and the hidden fields will appear, remove "hidden" class name from the fields, then remove ".pdc.hidden { display: block; }" from CSS section.

We are still working on the documentation for the new form JavaScript APIs, it is expected to be published in next week. You can refer to the documentation for Cloud before the self-hosted documentation is ready: https://doc.laserfiche.com/laserfiche.documentation/en-us/Default.htm#../Subsystems/ProcessAutomation/Content/Forms-Current/Javascript-and-CSS/TheLFFormObject.htm, some of the new APIs are not documented for Cloud yet. 

2 0
replied on January 12, 2023
0 0
replied on December 29, 2022

Hi Pieter,

We are not aware of such issue; can you open a support ticket and provide the exported process? Thanks.

0 0
View 5 previous replies
replied on December 29, 2022

Thanks, Rui-

I thought I found the problem, then spent a lot more time today than I wanted to digging in to find it for real.

It appears related to having lookup rules. A form with Field Rules but no lookups will save as expected, with field rules evaluated. However, add a lookup into the mix and the saved form will not have field rules evaluated.

I opened a case with LFC Support, 13562

0 0
replied on January 11, 2023

Hi Pieter,

I have received your process and tried to reproduce the issue. I tested saving to repository with form "Full Form" (with lookup rule) and "Full Form - Save" (no lookup rule), both forms could be saved to repository with field rule evaluated.

Can you record a video on how you reproduced the issue and post it here?

0 0
replied on January 12, 2023

Hi Rui-

Here's an mp4 of the behavior using a very simple example form I just put together. It's very easy for me to reproduce, as any time I try to save a form that uses the modern designer and lookups, field rules are ignored.

01.12.2023-08.10.31 (screencast.com)

0 0
replied on January 12, 2023 • Show version history

Hi Pieter,

Thanks for the video, I reproduced the issue following it. Actually I accidentally used a previous version of New Form so it worked for me when I first tested it.

I have reported it as a bug (id:409516) and we will fix it in next release. For now, can you keep a separated form without lookup rule as a workaround? Since lookup rules should not execute on save to repository form, it should have no harm to remove them.

Sorry for the inconvenience.

3 0
replied on January 13, 2023

Rui-

Luckily, it's a fairly easy workaround so not a big deal doing things that way until this can be resolved.

Thank you.

1 0
replied on January 21, 2023

I am having a similar thing at least since we went to 11 update 3 on Friday 01/20/2023 (we went to 11.2 a few weeks ago), only all fields are showing in the saved repository version.

There are lookup rules, but they are meant to show. All other fields are hidden by field rules in the Form but show in the saved version.

 

Attached is an example.

 

Any help is greatly appreciated. We have a hot deadline for this year's Financial Aid for students. Kinda big!

 

Thanks,

 

Frank 

Main Form-800277044-Smith Frank 1_21_2023.pdf (261.8 KB)
Download
0 0
replied on January 23, 2023

Hi Frank-

This is probably the same thing I'm describing. Make a copy of the form and delete all of the lookup rules on that copy. Then in your Save to Repository task, save that copy rather than the original. It should respect the field rules for hiding things.

1 0
replied on January 23, 2023

Hey Pieter!!

That did it.

It's a pain on single form processes, but on anything where data is being passed from from one form to another, any forms further than data collection step should have all their lookup rules cleaned out. They are unnecessary. I suspect they slow performance as well.

Good Tip!  Gives LF time to find the bug.

Thanks!

Frank

1 0
replied on February 14, 2023

Laserfiche has released the update for Forms 11 Update 3 with this bug fix, see more information from https://support.laserfiche.com/kb/1014419/list-of-changes-for-laserfiche-forms-11-update-3-hotfix-1014419

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

Sign in to reply to this post.

Details
Attachments
Related Posts
Loading ...