A custom Aurena Command Group button (ExecuteAction) doesn't respect a JSON-logic-style Enabled configuration expression the way a standard out-of-the-box button (like 'Create CO') does — the button always shows regardless of the condition entered. Is this supported for custom commands?

All FAQ questions / Platform, Aurena, and customization

Answer

At that point, this wasn't available for custom commands — the JSON-logic-based Enabled/conditional-visibility configuration mechanism was only wired up for certain standard, built-in buttons, not exposed for custom ExecuteAction command buttons, even though the same configuration syntax is used internally for standard buttons. This was acknowledged as a capability IFS was looking to implement for custom commands going forward — check current release notes for your IFS Cloud version, since this is the kind of gap that tends to get addressed over time rather than remain permanent.

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