Could you please address this as an Unplanned/Critical task. Also, if this is user error, could you please why.
Thanks,
Morgan
Notified 5 people
Harsh Parikh,Tech Lead
Hi
Paul
,
I checked and found that there is name in database that Gonzalo A Salazar Lizausaba has open that dispute on 25th August 2021. Hence, his name is show in Dispute UN/0300.
If you want to remove his name then let us know so we can remove his name from UN/0300.
Does this mean that because Gonzalo opened the dispute on August 25th and did not exit the document properly, it has stayed open in editing mode since that time?
If that's the case, we need to come up with a solution that prevents this from happening and automatically saves the document and checks it back into the database so that it can be edited.
Martin
, could you discuss this with
Harsh
and come up with a proposed solution.
Thanks,
Morgan
Notified 5 people
Martin Laporte,CTO
Hi
Harsh
,
Let's discuss this topic during our Tuesday meeting.
Thanks, --Martin
Notified 5 people
Martin Laporte,CTO
Hi
Morgan
and
Paul
,
You are correct that Gonzalo did not exit the document properly. He probably exited the application by closing the tab or the browser. There is no reliable way for our code to catch such an event.
There are 2 potential ways to deal with this:
We add a new button directly on the Admin page that would allow a user to "force remove" the name.
We run a regular SQL job that looks for situations like this one, and automatically removes the name when found.
I personally prefer #1, as we have a better control over the process.
Thanks, --Martin
Notified 5 people
Morgan Maguire,CEO
Understood. Thanks
Martin
. Could you please add the agenda for today's team meeting, and we'll decide on the appropriate solutions.
Also, here's a thought: would there be a need for the admin override if we allowed for simultaneous editing of master list records? If not, perhaps we should consider an option where we allow admin users to access the record at the same time. Given the task system we have in place, I'm wondering whether restricting access to a single admin user is necessary.
Thanks,
Morgan
Notified 5 people
Martin Laporte,CTO
Hi
Morgan
,
I will add this item to the agenda.
I wonder if these restrictions are in place to keeps things simple, in the sense that we only have one "master copy", and we do not have to worry about handling multiple versions and having to perform reconciliations between documents when ready to publish.
Harsh
, from a technical and functional perspective, what are your thoughts on allowing multiple users to work on the same document in parallel?
Thanks, --Martin
Notified 5 people
Martin Laporte,CTO
We discussed the possibility of capturing the "Session.OnEnd" event in ASP.Net. If we are able to do so, we could release/check-in any pending document under that user.
Perfect. Thanks
Martin
. I've approved item 1142 and put it in order 58.
Morgan
Notified 5 people
Martin Laporte,CTO
Hi
Paul
,
We have a fix on Staging that will be able to capture when a user exits ISLG Admin by closing their tab or their entire browser.
This should now prevent the original problem described by Morgan, where a document remains in editing mode when a user ungracefully exits ISLG.
Can you give this a test on Staging and report back here?
Thanks, --Martin
Notified 4 people
Paul Moon
Hi
Martin
:
Nafiseh
and I tested it on staging, and it seems to be working fine now.
Something slightly different that I notice these days is after
Irit
uploads an HTML on app.islg, I get the same admin override message here and there when I go into a document to assign tasks. Is this something that should be posted separately?
Thanks,
Paul
Notified 4 people
Martin Laporte,CTO
Hi
Paul
,
Yes, let's post this issue separately. I have a feeling there might be a relation between the 2, but I think it will be easier to track it on its own.
This is a low priority item.
Could you please address this as an Unplanned/Critical task. Also, if this is user error, could you please why.
Thanks,
Morgan
I checked and found that there is name in database that Gonzalo A Salazar Lizausaba has open that dispute on 25th August 2021. Hence, his name is show in Dispute UN/0300.
If you want to remove his name then let us know so we can remove his name from UN/0300.
Does this mean that because Gonzalo opened the dispute on August 25th and did not exit the document properly, it has stayed open in editing mode since that time?
If that's the case, we need to come up with a solution that prevents this from happening and automatically saves the document and checks it back into the database so that it can be edited.
Thanks,
Morgan
Let's discuss this topic during our Tuesday meeting.
Thanks,
--Martin
You are correct that Gonzalo did not exit the document properly. He probably exited the application by closing the tab or the browser. There is no reliable way for our code to catch such an event.
There are 2 potential ways to deal with this:
I personally prefer #1, as we have a better control over the process.
Thanks,
--Martin
Also, here's a thought: would there be a need for the admin override if we allowed for simultaneous editing of master list records? If not, perhaps we should consider an option where we allow admin users to access the record at the same time. Given the task system we have in place, I'm wondering whether restricting access to a single admin user is necessary.
Thanks,
Morgan
I will add this item to the agenda.
I wonder if these restrictions are in place to keeps things simple, in the sense that we only have one "master copy", and we do not have to worry about handling multiple versions and having to perform reconciliations between documents when ready to publish.
Thanks,
--Martin
If we are able to do so, we could release/check-in any pending document under that user.
I have created DevOps item 1142 to research this.
Morgan
We have a fix on Staging that will be able to capture when a user exits ISLG Admin by closing their tab or their entire browser.
This should now prevent the original problem described by Morgan, where a document remains in editing mode when a user ungracefully exits ISLG.
Can you give this a test on Staging and report back here?
Thanks,
--Martin
Something slightly different that I notice these days is after
Thanks,
Paul
Yes, let's post this issue separately. I have a feeling there might be a relation between the 2, but I think it will be easier to track it on its own.
Thanks,
--Martin