Skip to main content

When setting my role for a certain process flow, I noticed that the “Filter” was not enabled in “Meta”:
 

Set Filter allowed, but Meta is disabled

I had indeed not allowed “Filter” on the Subject and for the “Filter” I had set all columns to “Visible for filter” = “Never”.

It came to a surprise that my Process flow was actually working and indeed using the “Change filter” action.

Reading up in the documentation I see this:

Description under process flow action “Change filter”


I would think my situation is not conforming this statement as the Subject does not allow nor have any columns enabled for filtering.

The reason I had initially disabled the filter options, was that I wanted to prevent a user attempting to change a filter and later I decided the research my process flow options.

Now my main question is, is this functionality working as intended?

I am happy it works as it does now, but I want to be aware when this is not supposed to work like this and might get fixed, causing these flows to all brake when I decide to structurally apply them.

Hi Mark,

We are currently re-evaluating this process action.

There are two scenarios where this process action is used:

To fill in the filter screen for the user. This filter should allow for more conditions, filters look-ups by providing display values and can be removed by the user. May be used to simply supplement the current user filters.

To set an immutable system filter. This filter is not removeable by the user. As it is set by the developer, it use key values for look-ups instead of display values. Applying the system filter will probably remove the user filters, clears the search and will most likely reset to the default prefilters. The system filter acts as a hidden prefilter, the conditions are not visible in the filter screen and the system filter and can only be removed again by a process flow.

The former should require filter rights, whereas the latter should also work when the user doesn’t have the ability to filter.

Right now, the process action will function when the user has filter rights via the role, even when filtering is disabled on the subject. 

You can safely use the process action as is, we’ll set up a proper and ideally automated migration scenario when the working of this process action is revised.

Reply


Terms & ConditionsCookie settings