Implemented
2
[Feature Request] Classify Document after password removal
Source: paperless-ngx/paperless-ngx#12936 · opened by @OverDodo
Description The new password removal workflow is great, however it comes with two issues. Both are based on a simple Workflow triggered when a document is added, and then the action being the password removal. 1: ~~Even when the consumed document is not password protected, the workflow will create a new version of the document. In my opinion, it should not create a new version if the pdf did not have a password. Currently this would cause a ton of redundant data in the long run, when one cannot filter well in the trigger.~~ (Solved, thanks!) 2: When actually consuming a password protected doc, the suggestions (document type, correspondent, etc.) seem to be based on the original, where paperless did not yet have access to the contents of the file. This usually results in incorrect suggestions, since there is no content taken into account. After consumption and the password removal workflow, hitting the "Suggest" button in the document does suggest the correct fiel…
No pledges yet. Be the first to back this.
Comments
Similar requests
[Feature Request] "Document Deleted" / "Document Trashed" Workflow Trigger
6 votes · 0 comments
Document Retention Period / Automatic Expiration
9 votes · 0 comments
Optional password/PIN protection for shared document links
5 votes · 0 comments
Disable "Apply AI suggestions" workflow action on documents with no content
1 vote · 0 comments
[Feature Request] Approval Workflow
5 votes · 0 comments
No comments yet.