Hi Harsh ,

Paul has reported that the Legal Analytics teams has encountered some significant disruptions to their workflow (and a loss of work) resulting from the issues reported in the following to-do's: 

which relate to the following user stories on TargetProcess:

As a result, I have moved these to-do's to the Fix Immediately group, and request that you and the team resolve these issue as a high priority.

Let us know if you have any questions or concerns.

Thanks,

Morgan 

Hi Harsh ,

As an additional issues related to the to-do's above, Paul discovered a problem where he had a dispute form open and was making making changes to the fields over a period of time (approximately 20 minutes). During that time he was making changes to fields and was not static on the page, but he did not select "Save Draft" at any point. After finishing his review, he went to select "Save Draft" and then was time-out of his session, losing all his changes to the form.

I'm not sure if the above to-do's will resolve this problem, but we need to implement a system that will not timeout an admin user when they are review a form over a long period of time. The same should apply to the subscriber side when they are review a page. Timeouts should only occur if the user is static on the page.

I'll add this to agenda for discussion tomorrow morning.

Thanks,

Morgan

Hi Harsh ,

Further to the timeout issue above, could you please increase the timeout time to 120 minutes for the admin site? I discussed the issue with Paul , and 60 minutes still isn't sufficient.

Also, as we discussed, we should investigate the issue with how the application registers an interaction with the page that would reset the timeout timer. Currently, making modifications to data within Legal Analytics fields without saving the changes by selecting "Save Draft" isn't getting registered as an interaction. As a result, a person could make a series of modifications and lose their work if they don't save the changes within the timeout window. Ideally, the application would monitor and register any activity on the page (e.g., scrolling up/down the page or adding characters to a text field) and reset the timeout timer.

Thanks,

Morgan

Hi Harsh ,

Just following up on the discussion above, have we implemented the 120 minutes timeout window for the admin site?

Also, interested to hear your thoughts on whether we can change the way the site registers interactions with the page.

Thanks,

Morgan

Hi Morgan ,

We have implemented 120 minute time window in our local environment. But, Due to other changes are going on we are not able to deploy this change on server.

We are planning to release this change with other high priority admin side changes. 

Regarding, Interaction with page, we are not looking deeply in this but will discuss more in tomorrow call.

Ok. Understood Harsh ​. Let us know when the changes are deployed onto rebuild.islg along with the other changes.

I'll add the issue concerning interactions with the page to agenda for discussion tomorrow.

Thanks,

Morgan

Hi Morgan ,

As per our last call, We checked the session timer in our side. 

The session time is set ideal for 2 hours and it works. But, As you described, if user set on/off toggle after 1.5 hour then session need to increase again for 2 hours.

The session will be increased upon server call because session managed by server trip. (example, user click anywhere to pull the data, click on save draft, click on any menu link, contextual back link). if this kind of action user perform then session again increase for 2 hours.

But, if user only change toggle button or only type in text box or just scroll 
up/down then session timer will not increase because that time it is not interacting with server.

We can achieve this by programming at central level but we need to apply some logic or code and test it.

Let me know the priority of this. 

I suggest if it is not urgent then will take later on (in September month).

Hi Harsh ,

Thank you for investigating and confirming what gets registered as an interaction on the page. As you've suggested, let's get the 2 hour session time implemented, and we'll deal with resolving the non-server interaction issues during a subsequent phase.

In the meantime, Naomi , could you please get user stories written addressing these issues integrated into TargetProcess. I believe these are needed in all four projects (ISLG Admin, ISLG Subscriber, ILG Admin and ILG Subscriber). We want to ensure that this issues is addressed across both applications.

Thanks,

Morgan 

Hi Harsh ,

Following up on the issue above concerning the extension of the timeout timer to 2 hours. Has this been implemented on rebuild.islg yet? Paul , found that the issue is still present.

Also, Naomi Savannah , just a reminder that we'll need to have user stories written dealing with this issue in the long-term.

Thanks,

Morgan 

Hi Morgan ,

We extended the timeout for 2 hours. but, will check today again on rebuild.islg and will update you.

Hi Morgan , 

Please see the corresponding story here: https://industrialagency.tpondemand.com/RestUI/Board.aspx#page=profile&searchPopup=userstory/17745. If you are okay with this approach, I will go ahead and add the stories for the remaining three projects. 

Thanks, 

Naomi 

Ok. Thanks Harsh . Let us know when you've confirmed the 2 hour timer is in effect and Paul will run a test again.

Naomi , this looks fine to me (assuming the timer resets every time the user moves the mouse, scrolls, or clicks a button on the keyboard/mouse while in the browser - and any similar behaviours for mobile users). However, to be safe, let's increase the timer to 30 minutes.

Paul , note that this is a future change, in the meantime, the 2 hour timer will run until the user performs an action that makes a call to the server (e.g., saves data to the database).

Thanks,

Morgan 

Hi Morgan , 

Criteria updated to increase the timer to 30 minutes. 

Great. Thanks Naomi .

Harsh , please let us know what's happening with the 2 hour timer. Paul , has reported that this hasn't implemented on rebuild.islg. Note I've created a to-do to track the issues: 2 hour timeout window - TOLOGIX - ISLG App Rebuild.
   
Thanks,

Morgan