A Lobby filter condition using a literal '%' wildcard character (like UPPER(ITEM_DESCRIPTION) LIKE NVL(UPPER('%$CPF_NOME$%'),'%')) works correctly in IEE but doesn't return results in Aurena — removing the '%' characters makes it work in Aurena, but then it's no longer a partial/contains-style match.

All FAQ questions / Platform, Aurena, and customization

Answer

If a literal '%' character embedded directly in the condition string is causing problems specifically in Aurena, try building the wildcard using the CHR function instead of typing '%' literally — CHR(37) evaluates to the '%' character (37 is its ASCII code, confirmable via SELECT ASCII('%') FROM DUAL), so the condition becomes UPPER(ITEM_DESCRIPTION) LIKE UPPER(CHR(37) || '$CPF_NOME$' || CHR(37)). Building the wildcard via CHR(37) concatenation rather than a literal '%' character in the string has resolved this specific Aurena-only parsing issue for cases where a directly-typed '%' doesn't work.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Platform, Aurena, and customization questions