Feature request: Attachment panel support in Form Rules

1

It would be very useful if the Attachments panel could be controlled by Form Rules in the same way as regular form fields.

For example, functions such as:

* `ENABLE[Attachments]`
* `DISABLE[Attachments]`
* `MARK REQUIRED[Attachments]`
* `MARK NOT REQUIRED[Attachments]`
* `HIDE[Attachments]`
* `SHOW[Attachments]`


Use case

A workflow instance is assigned to a user as a task. Therefore, the user generally has modification rights to the instance.

Using the **Field Matrix** and Form Rules, we can already control very precisely which form fields the user may modify. For example:

`IF field1 = "Yes" AND userrole = "XYZ" THEN ENABLE[field2] ELSE DISABLE[field2]`

However, there is currently no equivalent mechanism for the Attachments panel.

A typical requirement would be:

`IF field1 = "Yes" AND userrole = "XYZ" THEN ENABLE[Attachments] ELSE DISABLE[Attachments]`

This would allow the user to always see/download existing attachments, while upload, delete, overwrite, metadata/category changes, etc. could be enabled or disabled dynamically depending on workflow data, user role or other conditions.

The same applies to **required attachments**. It would be useful to dynamically require at least one attachment depending on a Form Rule condition.


Current solution

Currently, attachment permissions such as **Add and delete** and **Edit file** can be configured in the Step Form configuration.

However, this does not cover the use case above because these settings are static for the step and cannot depend on form data, user roles or other runtime conditions.

Additionally, using different attachment settings for a specific step requires **breaking the form settings inheritance**. This is rather inconvenient from a maintenance perspective: a relatively small requirement such as making attachments read-only in one step requires maintaining a separate form configuration for that step.


Suggestion

Ideally, **Attachments should behave more like a regular form element** regarding Form Rules.

Supporting functions such as `ENABLE`, `DISABLE`, `SHOW`, `HIDE`, `MARK REQUIRED` and `MARK NOT REQUIRED` for the Attachments panel would allow attachment behavior to be controlled dynamically without breaking form inheritance.

It could also be useful to expose the attachment permissions in the **Field Matrix**, so that basic step-dependent configuration can be done there, while Form Rules could handle more complex conditional scenarios.


Thanks and best regards
Ernst