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

Question

Question

Form Dropdowns Populated via Lookup Rule Dont Display Value for Approval Form

asked on February 1, 2022

I have a form with multiple dropdowns that are populated by Lookup Rules.  The user submits the form successfully. However, when the approval step displays the same form (NOT read-only), the dropdowns no longer have a value selected. Is this a known issue?

0 0

Replies

replied on February 2, 2022

For the approval form, it is likely you need to remove the lookup rule. That way it simply displays the already set value and doesn't try to replace it with something.

0 0
replied on February 2, 2022

Hi Elexis, thanks for your reply.  The approval form is the same form as the one originally submitted, assigned to the user task with the

"Make form read-only for users the task is assigned to" checkbox not checked.

0 0
replied on February 2, 2022

Right so. What is the trigger for your lookup rule?

0 0
replied on February 2, 2022

There is no trigger, it's just a pick-list of possible values that comes from a database table.

0 0
replied on February 6, 2022

Hi Eric, 

What version of Forms are you using? I haven't recreated the issue with 10.4.5 nor found a known issue about it.

0 0
replied on February 7, 2022

Hi Ziyan,

 

Our forms version is

Laserfiche Forms Professional Version 10.4.0.1256

0 0
replied on February 7, 2022

Unfortunately I also haven't recreated the issue with a simple test form on 10.4.0.1256. Is there any JavaScript applied to relevant fields?

If further help is needed, kindly open up support case with your VAR and provide us the exported business process xml.

1 0
replied on February 8, 2022

Sometime I run into issues like this and find that recreating the form fixes the issue. Almost like the form got corrupt or something at some point.

0 0
replied on February 8, 2022 Show version history

Thanks for the replies.  This issue is happening with multiple forms that have been in production for a year or more.  So, it's something more universal to Forms itself though we haven't done any Forms updates.  But, yeah, could be some kind of forms database corruption (I hope not).  We've opened a ticket with our VAR.

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

Sign in to reply to this post.