Skip to main content
Solved

Process action change filters with wildcards

  • November 27, 2024
  • 2 replies
  • 86 views
B
Warrior
Forum|alt.badge.img+4

Hello, in the topic below the filtering option with wildcards is discussed. I'm trying to get this to work, but with no effect. When configured, i see the query being generated contains an ‘=’-sign and no percentages are concatted around the expression. What's the status of this? Is this still a bug, or should this work? We've just upgraded to the newest indicium/universal versions...

I have configured the column filter as contains in the subject

I've mapped the process flow parameter to the corresponding column in the process flow

I've allowed wildcards on the process flow action ‘change filters’. 

Allow wildcards in the PF step Change filter | Thinkwise Community

Interesting enough, i can see the extended filter showing a contains and the filter value. Which is correct, even though the query generates a ‘=’ without like operators. When i don't edit anything in the extended filter, and just confirm the preconfigured filtering options, they are applied correctly. Seems to me the query that is generated is incorrect. 

Best answer by Arie V

​@BramG ​@Eric Duivenvoorden We had to do some digging, but it seems that the Allow wildcards parameter in the Process action ‘Change filter’ has never been supported properly. The topic you refer to has resulted in a TCP (8858S), but that has not yet been picked up.

I’ll make sure to further discuss a solution internally, but don’t think you can expect a fix in the coming 3 months.

To make sure you are updated once a solution is there, I would suggest you raise a TCP issue as well.

View original
Did this topic help you find an answer to your question?
This topic has been closed for comments

E
Rookie

Any update on this?

Arie V
Community Manager
Forum|alt.badge.img+12
  • Arie V
  • Community Manager
  • December 5, 2024

​@BramG ​@Eric Duivenvoorden We had to do some digging, but it seems that the Allow wildcards parameter in the Process action ‘Change filter’ has never been supported properly. The topic you refer to has resulted in a TCP (8858S), but that has not yet been picked up.

I’ll make sure to further discuss a solution internally, but don’t think you can expect a fix in the coming 3 months.

To make sure you are updated once a solution is there, I would suggest you raise a TCP issue as well.

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings