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

Question

Posted to Laserfiche Lounge

Forms 11 - Saves/prints field data on page with extra codes.

asked on November 9, 2023

Prior to upgrading to Forms 11 yesterday, we had this issue in Forms 10.4.5. I had hoped that upgrading to 11 would solve this issue. It did change the code from one version to the other, but still needs to be fixed.

Here is our current config:  Windows Server 2016, IIS 10 and Laserfiche Rio 11_20231018 install.  We did an in-place upgrade from Windows Server 2012R2 to 2016.

Attached I have added both documents, what it did on 10.4.5 prior to 11 and after we installed 11. Hopefully, you can see what I'm talking about. In addition to these errors this particular form doesn't include the Action History page, but on those that do, it doesn't not write that page at all, it leaves the page blank.

 

I'm at a loss as to how to correct this issue and cannot upgrade our production servers if the Forms do not print / save correctly.

0 0

Answer

SELECTED ANSWER
replied on February 15

UPDATE to this issue:  We finally did an in-place upgrade to Windows Server 2022 and also updated to Forms 11, update 5.  At first, we still got the issue with the print/saved copy with formatting issues. Then contacted our VAR and after some time and troubleshooting with LF support, they suggested that we change the puppeteer path in Forms advanced config to Edge. Once the path was changed to the C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe.  we restarted services, and retried form.  The documents would process through as expected.

 

Issue Resolved.  Thank you to ImageNet (OKC) and LF Support.

0 0

Replies

replied on November 19, 2023

Hi Robin, could you please provide us this process for troubleshooting? We attempted to reproduce the issue on Forms 11U4 but were unsuccessful.

0 0
replied on November 20, 2023

I tried to upload the process, but it doesn't allow .xml files here. Any suggestions?

0 0
replied on November 20, 2023

Zhipeng,

So I have renamed it with .txt at the end, remove this to open process.

0 0
replied on November 20, 2023 Show version history

Hi Robin,

I cannot reproduce the issue on my env. It probably caused by you browser. So I recommend you to add the custom CSS below to try to hide the extra words enforce.

.screen-reader-legend { display: none !important; }
0 0
replied on November 21, 2023 Show version history

Okay I added this to my printed form only. However, I still have issues with the Table format and it is adding bullet points to some of the fields. (See attached)

 

Next, I went back and tried to add this CSS to each field with the bullets and it just removed those fields on the page.  We are making progress.  

As for Browsers, I am using Edge.  And once I create this form in our Test environment, (Ver 11) and import it back into Production (Ver 10.4.5 on Windows Server 2012R2) is it fine on all forms.  

Edge Version.JPG
0 0
replied on November 21, 2023

Another thing that happens, on some forms where the Action History page is included, that page is Blank.

0 0
replied on November 22, 2023

You can try to open the form in the Chromium (NOT Edge) browser of your test environment and check whether the issue occurs when filling the form.  If the extra codes issue occurs, you can try to reinstall the Chromium or remove suspicious extensions that may embed certain CSS styles in the page.

 

And as for the blank Action History issue, we strongly recommend you to open a support case if it still exists after you tried the steps above.

0 0
replied on November 27, 2023

I think there is a misunderstanding of my problem.

I do not have this issue when "filling out the form" only when it goes to Save to the Repository or when a file is attached via email notifications.

Once, I take the Test form in my new environment (2016/Forms 11) and upload it back into my Production environment (2012R2 /Forms 10.4.5) it is fine and print/saves correctly.

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

Sign in to reply to this post.