12.08.2026
15:13
It would be useful to have an option to configure the Attachment Category (Choice field) as required/mandatory.
Currently, an Attachment Category can be configured with a data source (fixed values, SQL, etc.), but there seems to be no option to make this field mandatory.
Use case
In many workflows, attachments are processed later depending on their category, for example:
Contract
Approval
Customer document
Technical documentation
Other
These categories may be used by actions, business rules, SQL queries, document generation or other workflow logic. Therefore, having attachments without a category can lead to incomplete or incorrect processing.
When a user uploads or drags one or multiple files into the Attachment panel, WEBCON correctly displays the attachment metadata dialog and asks for the category.
However, the user can confirm this dialog without selecting a category.
This is also reflected in WFDataAttachmets. For an attachment with a category, for example:
ATT_Attribute1 = '<ID>#Giro'
while an attachment uploaded without selecting a category is stored as:
ATT_Attribute1 = ''
The behavior is the same when uploading a single file or multiple files at once. For multiple files, WEBCON correctly displays the metadata dialog only once and applies the selected category to all uploaded files.
Suggested solution
Add a simple Required / Mandatory option to the configuration of the Attachment Category Choice field.
If enabled, the attachment metadata dialog should not allow the upload to be completed without selecting a category.
A validation on a workflow path could of course check afterwards whether attachments without a category exist, but this is not ideal from a UX perspective. The user may upload several files, continue working on the form, and only discover later when trying to move the workflow forward that one or more attachments have no category.
The better place for this validation is directly in the attachment upload dialog, where the category is entered.
As an additional enhancement, it would also be useful if the required state could eventually be controlled dynamically by Form Rules, similar to regular form fields, e.g.:
MARK REQUIRED[Attachment Category]
MARK NOT REQUIRED[Attachment Category]
But even a static Required option in the Attachment Category configuration would already cover the main use case.
