Hi Ricardo, you can submit the log files through Support, or through the test utility submission form located here: https://secure1.laserfiche.com/Forms/LfConnectorAppTests

We've also updated the Connector engine and test utility since the release. We don't have a new release yet, but Support will be able to provide you with an updated version of the utility if that turns out to be neccessary. 

Has there been any update to determine if Laserfiche Connector will work with JD Edwards EnterpriseOne? We have a client that is looking into this integration.

Ricardo, 

I don't believe we received any log files from you, we'd be able to help determine what's going on with them. You can use the submission page, or just pass them along through Support. 

Zaheer, 

We've had successful tests with some JDE applications, I'm not sure if that is one of them. 

Thanks!

Hi

can you please tell me the full path of the log files?

Thanks

The log files from the test utility are located in the 'My Documents' folder\Laserfiche Connector. The exact path differs by OS, but most times it's C:\users\<username>\documents\Laserfiche Connector. Log files from the main Connector application can be found at %APPDATA%\Laserfiche\Connector\logs.

We upload the log files today.

Thanks we'll look over them and get back to you. In the meantime, you might try the just updated 9.0.1 version of the Test Utility, we fixed a few compatibility issues in that, although I don't know if it specifically will impact this scenario. 

Ricardo, 

The log indicates you have never tried to uncheck "Use Javascript to detect fields instead of UI automation" on the first step. You might try to clear the option to see if it works.

Thanks!

Removing the checkbox "Use Javascript to detect fields instead of UI automation" does correct this as I ran across this same issue earlier this week.

Ricardo - Assuming this fixed your issue, I'm curious how the performance of the connector was?   My customer is experiencing about a 15 to 18 second delay (analyze screen) when they click the connector before it opens the scan interface.  Did you experience a similar performance hit?  If yes, was there a solution to this that you can share?   

Hi Brett, 

Are you using Connector 9.0.1? There were some performance issues specifically to the intitial read during runtime that were addressed in it. Note that UI automation is generally slower (just due to the technology involved) which is why it's the backup option. 

We tested with version 9.0.0.499.  I'll download the updated version and let you know the results.

thanks for the information.

Brett

Hi

When we run any of the connector options; we have a delay of 45 seconds before we have a response, we're using the 9.1 version of the connector.