(...) Hi Community, I’ve been using WEBCON for more than 2 years now, including the ocr AI engine. I must frankly say that I’m more than disappointed with the ocr results. I’m aware that it strongly depends on the quality of the incoming documents, but the AI buzzword increased my expectations. Now, with the complaining part done, I’m looking for a solution to the issue. The idea is to use an externa (...)
(...) script is faster than using formrules. As example i had a formrule what would get the sum of a number column in an item list and compare it to another field. It took sometime for the formrule to procr ess this, while my javascript that i wrote in a html element did it much faster. I wonder now if i should reimplement certain functions with javascript instead of using formrules to shorten the page (...)
(...) I am trying (without any success) to read data (ie. employee id) from an existing text-based PDF (test pdf created via MS Word). The documentation is explaining the different actions (ie. wait for ocr ai, wait for text-layer), but not how they actually work together or how to use them. Maybe I am completly wrong in trying to use "ocr AI recognition", "Wait for ocr AI" etc..... My goal is: * A (...)
(...) ndependent from the body type and should be accessible for mapping even when the response body is handled as binary stream / attachment. Typical use cases: * file download + metadata headers * ocr /AI APIs returning metadata in headers * presigned URLs * correlation IDs * filename/content-disposition handling 3. Add new response type "Text" / "Raw" Currently the action supports only: (...)
(...) Would it be possible to add a simplified view option via a button on the top bar that would display a different view of the form? This could work similarly to the ocr preview, where I could select which modules to hide—for example, attachments and comments. An example from my own experience is the invoice verification process. Users suggested that it would be helpful to be able to collapse the view (...)