Namespaces with filter

Filtered Namespaces allow you to limit the visible records to those that meet defined criteria. Filters are configured by an administrator in the process definition. As a result, users can only see records that match the configured filter on the form and do not have access to other data stored in the namespace. How to Configure Filters? Let’s look at an example. Assume that we have a namespace called Requests, which is used in the Orders process. In this process, users select items from the Requests namespace that they want to order. The Requests namespace contains a field called Department, which will be used as a filter. This ensures that users only see items assigned to the appropriate department. To use a field as a filter, you must assign an appropriate value to its Field key or Extension key property. This value is then used when defining filtering conditions within the process. The namespaces with filter extension includes an additional section for configuring filters: In the Field you can select from a list of fields available in the namespace. For each of these fields, you can assign a Field key or an Extension key. In the Key field, select the field or extension key that was previously assigned to the corresponding field or extension in the process. The selected key will be used when filtering data in the namespace. In the Operator field, you can define how values are compared. The following two options are available:

• Equal – values must be identical,
• Like – values are compared partially.

In our example, the filter will be configured as follows: You can define any number of filtering conditions; the system does not impose any limits on the number of filters. However, it is important to remember that overly restrictive or incorrectly configured filters may limit the availability of records. Therefore, the administrator should define filtering criteria in a way that allows the user to select the appropriate items and correctly carry out the process. After selecting Administration in the Department field, the list of requests will be automatically limited to items assigned to that department: The filter is defined by the administrator and works automatically. The user has no option to remove it.