Core routing framework
When a user selects a message link, the destination is resolved using this order:
- Identify the click source and the user's default portal, for example SSP or Admin Portal.
- Attempt to open the target feature page in the preferred portal for that click source.
- If the user does not have access to the destination page or portal, attempt the alternate portal, if supported.
- If the user lacks access to both portals, an error message is displayed indicating that the page or portal is not accessible.
Click sources and routing preference
These routing preferences are applied based on the click source.
| Click Source | Routing preference |
|---|---|
| Admin Portal workmail | Open the Admin Portal destination. Fall back to SSP only if an Admin Portal destination does not exist. |
| SSP messages | Open the SSP destination. Fall back to the Admin Portal only if an SSP destination does not exist. |
| Notification Center, external mail, Workspace Widgets | Open the user's default portal. Fall back to the other portal if required. |
Note: Routing does not bypass feature configuration. If a page is hidden or disabled by configuration, the link cannot force the page to open.
Post-authentication drillback (external email)
When a user clicks a link from external email with no active session, the user is prompted to authenticate. After successful login, the user is redirected to the intended target feature page, subject to the same access checks and fallbacks.
Some environments, such as direct access without Infor OS, or certain mobile containers, may not support all drillback flows. Validate behavior in your deployment.