connector - Chrome and Windows 10

asked on May 27, 2020

Does anyone have issues or solutions for running Laserfiche Connector (LFC) in Chrome? Over the past year Chrome updates have broken LFC for us and we've been able to get workarounds after the fact. I thought I would see a lot of posts about this on Laserfiche Answers but that isn't the case. So it would be helpful to hear what others are doing to keep LFC up and running through Chrome updates.

We have also had many issues with LFC on computers running Windows 10, which most of our pc's are running. Our Windows 7 profiles would not work on Windows 10 pc's, so we created new profiles for Windows 10.

Then when Windows 10 updated to version 1903, our Windows 10 profiles would no longer work. We worked with our vendor extensively at this time and even had a meeting with a Laserfiche developer where the issue was demonstrated. After this, it didn't seem that the problem was fully acknowledged by Laserfiche, so we had to create a new set of profiles for Windows 10 version 1903 and above.

We found out yesterday that when Chrome updates to 83.0.4103.61, that our newest LFC profiles for Windows 10 are no longer working.

What are we doing wrong? Has anyone else been able to work through issues with LFC with Chrome and Windows 10? We really love the product but find it difficult to keep it up and running.

Thank you!

0 0

replied on May 28, 2020

Hi Sarah,

We made some simple tests on Chrome 83.0.4103.61 on Windows 10, and the simple profiles work.

I recommend you to ask your vendor to create a support case, and provide the following information, then we can investigate what is the root cause and help you to keep Connector up and running.

Your profiles that cannot work;
Log files:
1. Exit the Connector, and open Connector again (to make the log files clear)
2. Run a profile that cannot work
3. Go to folder that store log files, and copy the latest one
4. Exit the Connector, and open Connector again
5. Create a new simple profile on the website you meet issues, i.e. search a word that is retrieved from your target website
6. See if the new profile works
7. If not, go to the folder that store log files and XML files, and copy the latest files

2 0

View 6 previous replies

replied on June 1, 2020

Hello and thank you for the response. We did work with our vendor on this and a case has been opened. All in all, I must say that LF Connector has been extremely high maintenance for us because browser updates break it and we've had numerous issues with computers running Windows 10--which most in our organization are on.

0 0

replied on June 4, 2020

Hi Sarah,

Thanks for your information. Can you share your previous and current support case IDs? Then we can investigate more based on real scenarios and see if there are anyways to enhance it.

1 0

replied on June 4, 2020

Hi Tianxia,

Our major cases are the current one, #209585, and last year's, #203628. Thank you so much for looking at this!

2 0

replied on August 11, 2020

To close off the thread, the 2 issues in the support cases mentioned above were due to breaking changes in how Chrome displays URLs and names elements on the page. The first one was patched in KB 1014068. The second one, unfortunately, is more involved, so we cannot patch it, nor can we protect against future breaking changes.

We are looking at our procedures to at least try to stay ahead of these changes and announce known issues or workarounds closer to the browser's new version releases.

1 0

replied on August 11, 2020

For the second one, as Miruna explained, we are looking at our procedures. An extra suggestion for anyone who meets similar issues is that, using the Javascript method if it works. This method is more stable and can minimize impacts, as it depends on the website itself, not on Chrome/OS. That is, as long as the ERP application is not upgraded, it will work as expected.

0 0

replied on August 17, 2020 • Show version history

Hello and thank you for the response. I am attempting to recreate one of our LF Connector profiles using javascript and can't create a token for a field within an iframe. When I drag the target button onto the page, the entire frame outlines in red but I choose a field within it.

0 0

replied on August 17, 2020 • Show version history

Hi Sarah,

Sometimes, once the entire frame is focused with red outlines, the Connector cannot recognize its inside fields. At that time, you can try to drag the target button out of the frame and the red outlines will disappear, and then quickly drag the target directly to the field that you want to recognize, and see if it can be focused with red lines.

0 0

replied on August 28, 2020

I put some time into trying to make that happen, but it still won't recognize the inside fields.

Thanks for your response!

0 0

replied on August 30, 2020

We are uncertain about the root cause of the issue through the above description. If you'd like to solve the Chrome update issue by creating profiles using the Javascript method, I recommend you to send us the profile and comment on which fields cannot be recognized in the support case.

0 0

Question

Question

connector - Chrome and Windows 10

Replies

Sign in to reply to this post.