In my experience a common request is to have some process started when a user logs into the system, or when they log off. For example every time a user logs in we want to hit an API hosted by another system to get the users data to be used for privilege's in our Appian instance.
A similar request is every time a user logs out to start a process. This could be to purge the old user data.
I know one solution is to have a timer based model getting all users data, but for this use case that's not possible because they want the data fresh as 15 min of log in.
Another solution could be to use a start page all users must hit with a start process link, but then I still have the issue if they save a url they could just bypass the start page.
Discussion posts and replies are publicly visible
Just some thoughts ...
With SSO and SAML there is a way to synchronize group membership on login.
Logout is difficult because you always need to wait for session timeout.
There are more ideas I prefer to not tell to everybody. Personal message if you're interested.
Why is all that necessary?
It could be something as simple as a customer with a super strict requirement to track all user logins in real-time and in a way that's trivially easy to access from the development front-end and spawn logic like manager notifications or account soft-lock, both of which i've seen before, and both of which required ridiculous bend-over-backwards style solutions.
© 2021 Appian. All rights reserved.