hello, y have a problem with the session variables, when they is finished and the user do a action, I´d like to show login page. do you know how?
Yes, there is a way to do this, I have some sample code put together but it was an internal item so I can't really share it. Basically you push the session id into some JavaScript, then write a REST service that looks up the session to see if it should still be active or not, have the JavaScript call that REST service every minute or so, and once it gets "user session is expired" from the REST service, make sure that the user's authentication cookies get cleared and send them to the login page.
J.Ja
Is there any way to give the user some feedback and ask them if they want to cancel the timeout, just in case they don't want to be logged out?
Alan -
See this sample code:
https://www.outsystems.com/forge/component/1886/login-session-timeout-sample/
It can easily be edited to meet your needs.
Such monstrous workarounds for such a simple task. That's the beauty of Outsystems.
Alexander Hagen-Thorn wrote:
I would say that the beauty of OutSystems is that even when you need to do a "monstrous workaround" to something, having a good team, you still are able to deliver your application (with quality), much faster with fewer developers than the ones that would be needed if using a different technology. With the advantage of being easier to maintain the application later... :)
Nevertheless, what would be a way to solve this in OutSystems, from your point of view? I mean, what would you change in the OutSystems platform to simplify this task?
Cheers!
Eduardo Jauch wrote:
Hi Eduardo,
To simplify this particular task, it would be nice if Outsystems support the session timeout per-application as an easy accessible setting. Probably the same thing you do with your extension, just to have it out of the box.
It is not a problem that this particular feature is not there, but this is an example of a common problem we have with systems of this kind: if a feature is not included, it becomes considerably harder to do the thing than it would be with bare vanilla technologies (like ASP.NET in this case). In this example, instaed of adding a single line of code to my project, I have to involve all the extension-making machinery.
I agree, you are still able to deliver. And this creates an illusion of success, even if you spent more effort than you could otherwise.
I have worked with Outsystems for about a year by now, our company parntered with Outsystems, and this collaboration is a crazy success from managers perspective: we have new clients (attracted by easy and quick delivery motto), we have new projects, and we are able to deliver -- so nice! But as a developer, I often suffer and remember the metaphors of "trying to paint the room through a keyhole" and "getting the monkey and the whole jungle when you only need a banana".
So my opinion is: Outsystems is a successful marketing project, which really helps to make profit, but it is not a good development tool.
I mean, if you give Outsystems to unexperienced developers, they still will produce crap. That is why you have to provide all those tutorial cources and certification system. But an experienced developer will feel more comfortable with vanilla technologies.
I am sorry for the offtop here. I probably should not make my comment in the first place, it was just emotional.
Hi Alexander,
You say that your managers are happy, the customers are happy, and that you are able to deliver.But you are not happy.
I think you are not happy and have this impression that OutSystems is not a "good" development platform, because you are focusing on the wrong things.
An OutSystems Team with 1/3 of the number of (good) developers deliver a fully functional and high-quality application in 1/3 of the time it would be required if using "vanilla" technologies. And this in the wors case scenario. I saw much better.
That's what makes your managers and customers happy. This is not marketing.
In the end, all technologies have things that are easier or harder to do on them. What matters is the time it takes for you to deliver the solution, with good quality.
OutSystems will not make out of anyone a good developer, as much as any other language/development tool. And like any other development tool, you need to learn how to use it. OutSystems is a Low Code platform, not a No Code one. You are still developing.
In the end, I don't agree that an experienced developer will feel more comfortable with vanilla technology. I am one, and I know a lot of them, and very few of them, after starting working with OutSystems, wants to work with vanilla technologies again.
Of course, many of them would if it pays better ;)
If you'd like, we can continue this conversation in private (to avoid a long thread on a closed topic). I would like to know your experience in OutSystems to understand better why it makes you feel like you say. :)