35
[Feature Request] Define custom fields as required (mandatory)
Source: paperless-ngx/paperless-ngx#11107 · opened by @andreaswaefler
Description Hi team, I'd like to suggest a feature enhancement: the ability to define custom fields as required (mandatory). Use Case: When working with documents, some custom fields are critical and should not be left empty. Right now, custom fields are optional by default, and there's no built-in way to enforce their completion when i see it right. Proposal: Add a setting when creating or editing a custom field to mark it as required. When saving a document, the system should check that all required fields are filled before allowing the document to be saved. The UI should provide clear feedback if a required field is missing. Benefits: Ensures important information is always provided Improves data quality and reliability Helps prevent incomplete document metadata Thanks for considering this improvement! P.s. It may be necessary to make an exception when the document is first created and for the flows so that it does not generate an error when …
No pledges yet. Be the first to back this.
Comments
Similar requests
[Feature Request] Nested Custom Fields and Custom Fields of Type Class and List
12 votes · 0 comments
[Feature Request] Using custom fields in workflow title templates
32 votes · 0 comments
[Feature Request] Add Custom Fields Support to Correspondents, Document Types, and Other Entities
27 votes · 0 comments
[Feature request] Allow ordering of custom fields
58 votes · 0 comments
[Feature Request] Password and MFA enforced Policies
2 votes · 0 comments
No comments yet.