In OutSystems, when a user tries to access a specific page without an active login session, they are redirected to the login page. However, after successfully logging in, the user is not redirected back to the original URL they attempted to access. Instead, they are sent to the default portal or home page.
This behavior can be inconvenient from a user's perspective. Users are forced to manually navigate back to the desired URL, which disrupts their experience, especially in scenarios where deep links or bookmarked URLs are involved.
Proposed Solution: Modify the authentication flow so that if a user is redirected to the login page due to an inactive session, their original URL is preserved. After a successful login, the user should be redirected to the URL they initially attempted to access, rather than the default portal or home page.
Benefits:
- Improved user experience and satisfaction.
- Enhanced support for deep links and bookmarked pages.
- More intuitive behavior aligned with common expectations for web applications.
This enhancement would make OutSystems more user-friendly, particularly for scenarios requiring frequent logins or when users access the application via shared links.