Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modify "Only available with Pro/Enterprise" text in /documents/{id}/ocr endpoints #227

Closed
reganwolfrom opened this issue May 26, 2024 · 0 comments
Assignees
Labels
documentation Improvements or additions to documentation
Milestone

Comments

@reganwolfrom
Copy link
Member

Now that OCR with Tesseract is available in all editions of FormKiQ, there should no longer be messages about being only available.

However, we will want to include new messaging about how the Textract option (with tables and forms) is only available with Pro/Enterprise for the POST endpoint.

Maybe this?

"Document optical character recognition (OCR) request; extract text and data from a document; Tesseract available for all editions, but Textract engine and tables and forms options ONLY available with FormKiQ Pro and Enterprise"

@reganwolfrom reganwolfrom added the documentation Improvements or additions to documentation label May 26, 2024
@reganwolfrom reganwolfrom added this to the v1.15.0 milestone May 26, 2024
mfriesen added a commit that referenced this issue May 29, 2024
mfriesen added a commit that referenced this issue Jul 7, 2024
mfriesen added a commit that referenced this issue Jul 7, 2024
* 215 - Add "ocrNumberOfPages" to OCR action

* #207 - GET /documents/{documentId}/content - NoSuchKeyException

* #217 - deepLinkPath property is using the deepest-level name as path and is not modifiable

* #218 - POST /search tag range not inclusive of "end" value

* #228 - add IDP Mapping

* #227 - Modify "Only available with Pro/Enterprise" text in /documents/{id}/ocr endpoints

* #226 - Add ability to publish document

* Updated console to 3.6.0

* #232 - Add Schema Classification

* #231 - Require valid URL on deepLinkPath property

* #195 - Users API
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants