Excursus: Role filter: Works like the filter in the filtered archives and restricts the number of visible processes. This makes it possible to give different roles different views of an archive without having to create additional filtered archives. In role filters, all columns can be used for filtering that are also possible in filtered archives, i.e. also the dynamically generated columns such as remarks_count and postbox_users. In addition, role filters that are configured for summarised archives in roles are also taken into account. It is therefore possible to display more processes to a user in a summarised archive via the role filter than would be directly visible in the archive. In the API and the filters (e.g. role filter or in filtered archives), there is a postbox column that indicates via true or false whether the process is in the mailbox of the calling user. For example, the following role filter can be used to make only those processes visible in the archive that are currently in the user's mailbox anyway:
postbox = true
If you want to filter on a field with empty content, you should use the comparison value <empty>. This stands for both empty and "null"._custom_field = <empty>
An expression accessed = true can be specified for role filters.
This filter returns all processes to which a user has already had access.
This is the case in the following situations: The task has been created. You had the task in the mailbox yourself, either directly or via an appointment. You would have had the task in the mailbox, but the deputy was currently active and the task was sent directly to them. The case was in the mailbox via a group.
It is also possible to access record: fields in the role folder. This allows a key value field of the archive of the currently selected role to be filtered for references in another archive, for example.
Filter on history: In the column search, there is a hidden (i.e. not selectable in the interface) history field that can be used to filter for the existence of certain history entries in the role filter or in filtered archives, for example.
history.action: Filters for messages that were created by the workflow action routine "Write history entry".
history.creation_date: Time of the history entry.
history.user: The user name from which the history entry was created.
history.user_id: The internal user ID from which the history entry was created. This ID is only written for all history entries added from version 7.1.3.
As with the filters for sub-table values, all processes are displayed for which at least one history entry exists to which the filter applies.