A Custom Page is correctly available as a navigation target for a new Aurena Command on another window, and shows up correctly in the target-page dropdown — but when configuring which page attributes to pass through as navigation parameters, the attributes dropdown for that custom page shows nothing at all.

All FAQ questions / Platform, Aurena, and customization

Answer

At the point this was raised, this was a known limitation/issue with custom pages specifically as command navigation targets in Aurena — the navigation-parameters attribute list wasn't populating for custom-page targets the way it does for standard pages, and the recommended path was to report it to R&D as a case for correction in an upcoming update rather than expecting a client-side configuration fix. Check current release notes or open a support case if you hit this on a recent track, since this may have since been corrected.

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