Anyway to detect Timeout or Browser closing as Logout?

BenHayat

Hi;

In aware, we have notification rule that gets activated when a user normally logs out. We use both Login and Logout rules in our tracking system to take certain measurements.
However, if a user just closes the browser (while in Aware app) or just let it time out, we don't get any entry that the system eventually logged out at a specif time.

Is there a way to capture or execute the rule when user closes browser or times out, so we will have a log out entry?

Thanks!

BenHayat

The reason I asked this question, because I had seen an application that did detect when the browser had been closed and time-stamped the closing. I didn't test to see if it would detect timeout too. I'm sure since they had set the timeout range, they could have calculated the timeout moment and track that as well.
But I'm not sure if there ways in Aware that we can use.
Just asking...

tford

You can access the IsTimeout attribute in the Logout Notification rules. AwareIM can not ID when the user has closed the browser that I know about.

BenHayat

Hi Tom;

I use the Logout event of Aware to create a new object, as Aware "determines" when the logout happens and automatically runs my rule.

So, I'm not sure where and how I can use that attribute, since Aware doesn't see "Timeout" event as a logout event to execute my rule. Therefore, what would that attribute can offer me?

Can you explain how this attribute and the Logout event correlate with each other?
Thanks!

tford

I can confirm that timeouts do in fact trigger the "When logout notification is received" and the the IsTimeout attribute is available.

This is in the Initial Value field of an OutgoingEmail notification that fires in one of my BSVs on Logout:

I have also included the IsTimeout attribute in login/logout logs I have in a few BSVs and can once again confirm that IsTimeout is captured appropriately in the logs.

BenHayat

tford wrote
I can confirm that timeouts do in fact trigger the "When logout notification is received" and the the IsTimeout attribute is available.

This is in the Initial Value field of an OutgoingEmail notification that fires in one of my BSVs on Logout:

[attachment=0]logout.jpg[/attachment]

I have also included the IsTimeout attribute in login/logout logs I have in a few BSVs and can once again confirm that IsTimeout is captured appropriately in the logs.

Ok, maybe I'm understanding you now.
Firstly, I don't care if the logout was resulted from normal logout or timeout, as long as Aware executes the rule, so having this in mind, are you saying:

a) Aware DOES invoke the logout event (rule) when a timeout takes place?
b) Also, the IsTimout attribute provide info if the logout was the result of timeout. Is that what this attribute for? If yes, it good to know, but doesn't help me much.
My original question was if timeout is also captured logout event, which I think you're saying "Yes".

tford

Yes and yes.

It's simple to prove it .. just try it & be sure you are capturing IsTimeout value in your rule. That's how you will prove it.

BenHayat

Yes Tom, Timeout did trigger the logout event and I see a new entry in my DB, I had tested it before, but for some reason it didn't work before.

Some applications if you try to change tab or close browser, they detect it ans give you message and capture the time too. I wish Aware could capture Browser close as well.

BenHayat

Too bad within Login event I can't detect if the user logged in from Desktop or Mobile. In it the source in the login event object, so I can not have another process to create it in the VP Init to capture the source. I wish Aware would provide (through browser agent) if the source is a desktop or Mobile during login event.

mrbdrm

you can pass the user agent from the logon page in a hidden filed with a init process
I pass the user agent and country code with no problems
you only need to update the logon BO entry with the additional user agent from a process rather than from the logon otification

BenHayat

mrbdrm wrote
you can pass the user agent from the logon page in a hidden filed with a init process
I pass the user agent and country code with no problems
you only need to update the logon BO entry with the additional user agent from a process rather than from the logon otification

Oh yes, I remember BobK gave you a tip on that. I need to look into it. Thanks!