Is it possible to use "like" operator in a!queryFilter?

@ramakg Define the filter values for each filter. For instance, if 'Complete' is chosen as filter value, what kind of data would you like to filter?

Example:
If you would like to filter portal report data based on values 'Registration Completed', 'Setup Complete', 'Completed' when 'Complete' is chosen as a filter, the queryFilter should be constructed as follows:
if(
\tfn!like(
ri!tStatus,
"*Complete*"
),
a!queryFilter(
field: "c3",
operator: "in",
value: {"Registration Completed","Setup Complete","Completed"}
),
\t{}
)

On the similar lines, choose a set of values with which you need to filter the portal report based on the value of ri!tStatus.

As said by other practitioners above, even "includes" (without usage of asterisks) should do the job. I would suggest verifying the validity of the expression fn!like(ri!tStatus,).

@ramakg Define the filter values for each filter. For instance, if 'Complete' is chosen as filter value, what kind of data would you like to filter?

Example:
If you would like to filter portal report data based on values 'Registration Completed', 'Setup Complete', 'Completed' when 'Complete' is chosen as a filter, the queryFilter should be constructed as follows:
if(
\tfn!like(
ri!tStatus,
"*Complete*"
),
a!queryFilter(
field: "c3",
operator: "in",
value: {"Registration Completed","Setup Complete","Completed"}
),
\t{}
)

On the similar lines, choose a set of values with which you need to filter the portal report based on the value of ri!tStatus.

As said by other practitioners above, even "includes" (without usage of asterisks) should do the job. I would suggest verifying the validity of the expression fn!like(ri!tStatus,).