Hi,I have an hybrid application, the 'Single Sign-On Between App Types' has been working without too many problems.
We have a bit of logic to prevent concurrent sessions and for that in the Reactive side we are using some client variables.We are having some weird behaviours when the user logs out of the app. We have distinct behaviours for when the user logs out through a Traditional or Reactive module:
- When logging out through the Reactive module the client variables reset to their default values as expected;- When logging out through the Traditional modules, the client variables continue there without any changes;
It looks like a bug from the platform, ignoring the fact that SSO between app types is enabled.Any ideas on how to fixe the issue? Am I missing something?
Best regards,
José Pais
OutSystems documentation states that client variables should reset to default values upon user logout. However, because Traditional modules can't directly access these variables, they don't automatically reset when a user logs out from a Traditional module. This behavior difference stems from the architectural distinctions between Traditional and Reactive modules. As a work around ,consider explicitly triggering a Reactive app URL during the logout from a Traditional module.
@Siya Thanks for the work around. I will try it.Hopefully it works.
OS says that is able to handle hybrid applications, therefore it looks like a simple use case that needs to be validated as well.Really hope they fix it.