A custom-event-driven notification's click-through link opens the right page but doesn't filter to the specific record, even though the equivalent worked in the on-premise client.

All FAQ questions / Platform, Aurena, and customization

Answer

The on-premise external-search URL syntax doesn't carry over — the working pattern in the current web client is a page URL with a $filter (or equivalent semicolon-separated filter) expression naming the actual key fields and their values directly, rather than the old external_search=OBJKEY=... convention.

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