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

Question

Question

Recent collection changes in Cloud?

asked on May 17, 2023

Has Laserfiche changed anything recently with regards to the functionality of collections? I've noticed a few things:

1. Previously, if I went to an active instance of a form and clicked "Edit" on the Variables tab, and tried filling in a multi-value field (such as a single-line text field in a collection), every time I filled in a value, it would automatically display another line so I could enter a second value, then a third value, and so on.

Now it only shows one field no matter what, making it impossible to enter multiple values.

2. I had a form where a section would be shown via Field Rule if a certain field in a collection was not blank. Previously this was working, but now the section is shown no matter what.

3. I had some jQuery on a form that would iterate through a collection, retrieve a URL from each row, and use that URL to populate an iframe. That was working before, and is now not working. Even code that iterates through the collection to print out the value of each field with a certain class is just printing "undefined"

0 0

Replies

replied on December 21, 2023

Hi, we have supported updating variable value with changing collection sets/table rows for in-progress instance on Forms 11 Update 5.

You can see other changes from:

List of Changes for Laserfiche Forms 11 Update 5 - Knowledge Base

Get Forms 11 Update 5 from Laserfiche 11 package:

Software versions and fixes included in the Laserfiche 11 Download Package - Knowledge Base

2 0
replied on December 21, 2023

Hi Lu,

Some of these changes seem very helpful, but this post was about Cloud. Has that change been made to Cloud?

0 0
replied on December 21, 2023

Hi Brian, we just support this feature in self-host Forms for now. No changes for Cloud yetblush

0 0
replied on May 18, 2023

Hi, the followings correspond with what you've noticed.

1. The multiple values depend on the submitted Form. In the submitted form:

and it will be displayed like:

 

For 2 and 3: could you please provide the process files that can reproduce the problems?

0 0
replied on May 18, 2023

Hi Zhipeng,

 

The issue with #1 is that if a field in a collection has nothing in it upon form submission by mistake, we have no way to populate it with more than one value from the Monitoring tab.

 

For #2 and 3, things seem to be working in a simple test process I made, so there must be something else causing the issue within the process I'm having the problems with.

 

Thanks,

0 0
replied on May 18, 2023

For #1, we will take it into consideration of feature request.

For #2 and 3, you can propose a support case with the problematical process so that we can troubleshoot better.

0 0
replied on May 19, 2023

Hi Zhipeng,

 

For #1, if you're wondering why not just make the field required, in the process in question it is populated by a workflow.

 

For #2, for more information, it seems that using a "Show if" Field Rule where the condition is "[empty field within collection] is not empty" will show whether or not it is empty. In fact, if you say "all conditions are true" and have one condition as "[empty field within collection] is not empty" and another as "[the same field] is empty" it will show even though it's impossible for it to be empty and not empty at the same time.

 

For #3, this seems to have been caused by the fact that the form was assigned to a team. When I assigned it to myself, things started working.

0 0
replied on May 19, 2023

Hey @████████ - #1 sounds like the same thing requested in November 2022 via this post.  Maybe it can be bumped in priority since there are several of us requesting this?

 

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

Sign in to reply to this post.