A Custom Menu's condition works fine when defined against a single language (checking that STATE isn't 'Planned'), but as soon as translated versions of that same condition are added for multiple languages, the custom menu stops appearing at all.

All FAQ questions / Platform, Aurena, and customization

Answer

Use OBJSTATE instead of STATE as the condition field — OBJSTATE holds the underlying, non-translated status code (consistent regardless of the user's language), while STATE reflects the translated display text, which is what breaks when you try to define the same logical condition across multiple language-specific values. Switching the condition to check OBJSTATE against the underlying state code works correctly for all languages without needing a separate translated condition value per language.

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