Similar to Erroneous admin override message - TOLOGIX - ISLG App Rebuild for Tologix, I am getting an erroneous admin override message without identifying who is currently "editing" the document when there is nobody actually editing the document. Any admin override message should now identify the person who is editing the document, but the message does not contain that information.
Can you investigate and add as an unplanned item if necessary?
Thanks, -Martin
Notified 2 people
Harsh Parikh,Tech Lead
Hi
Paul
,
Irit
and
Martin
,
This task is done on staging.islg. Now, Any admin user will close the browser or tab directly then admin user is automatically logout for that particular document.
You can check on staging.islg and give your feedback.
Notified 3 people
Paul Moon
Hi
Irit
:
When the next HTML comes back, could you try to upload it on staging.islg to test this? Please continue to assign the final step "Publish" to
Nafiseh
for this test.
Thanks,
Paul
Will do.
Notified 4 people
Irit Weinfeld
Hi
Paul
, I uploaded the HTML for IC/0565/11 on staging.islg. I assigned the final step to Nafiseh as you requested above.
Thanks, Irit
Notified 4 people
Paul Moon
Hi
Harsh
:
The issue is resolved on staging.islg, thanks.
Paul
Notified 4 people
Paul Moon
Hi
Harsh
:
I see this was DevOps #1370 which was deployed to production as in DevOps #1387. However, as shown in the video below, this is not resolved on app.islg
1. After HTML is uploaded and any of the 6 tasks is assigned, it should not trigger an admin override unless somebody is actually editing the document.
2. An admin override message should identify who the person editing the specific document is. As shown below, it simply says "another user." It should identify the name of the person who is supposedly editing.
Martin
: if we need to approach this error from a different angle, please feel free to create another DevOps item.
Thanks,
Paul
Notified 4 people
Harsh Parikh,Tech Lead
Hi
Paul
,
This change was revert back as there was an issue on Tuesday. Today, We again newly uploaded this change on app.islg.
As per your above comment, there is no need of second change. because once admin use close the browser window /tab/logout from admin then that message will be disappear.
It means no one is working on that document.
Please check again and let us know the feedback.
Cc :
Martin
Notified 4 people
Paul Moon
Hi
Irit
:
Could you let me know when you upload an HTML file the next time for me to test this?
Thanks,
Paul
Notified 4 people
Irit Weinfeld
Hi
Paul
,
I uploaded the HTML for SC/0015/107 on app.islg. I assigned the final step to Nafiseh as you requested above in this thread.
Thanks, Irit
Notified 4 people
Paul Moon
Thanks,
Irit
.
Harsh
: the problem is resolved, thanks.
Paul
Notified 4 people
Paul Moon completed this to-do.
Paul Moon re-opened this to-do.
Paul Moon
Hi
Martin
:
As you see below, there is a regression issue with the erroneous admin override message (without identifying who the editing admin user is) still appearing. As far as I know, nobody is working on UN/0133/28, and Eleo may not have exited the document properly. How can we actually resolve this issue?
Did you just encounter this issue in the past 15 minutes?
Nafiseh
and
Irit
both experienced issues with being logged out of the Admin Dispute Document page, so
Piyush
just replaced the file with an older, more stable version, which might be the cause of the regression issue you are seeing.
--Martin
CC:
Harsh
Notified 5 people
Paul Moon
Hi
Martin
:
Yes, the video was recorded about 15 minutes ago.
I have been experiencing getting kicked out of the admin dispute document page for days, but I haven't been able to record it to show what triggers the problem. I still got logged out right before I recorded the video above this morning.
Thanks,
Paul
Notified 5 people
Martin Laporte,CTO
Hi
Paul
,
For now, we are using a page that is a bit older, but more stable.
Harsh
is planning to investigate the issue, and our goal is to restore the latest page/functionality once we have isolated the "auto logout" issue.
Harsh
: please post your progress in this thread. Thanks.
--Martin
Notified 5 people
Paul Moon
Thanks,
Martin
.
DevOps 1427 is marked done. Should we change the status or create a new item?
Paul
Notified 5 people
Martin Laporte,CTO
Hi
Paul
, I have reopened task 1427.
Notified 5 people
Paul Moon
Hi
Harsh
:
This is supposedly deployed via DevOps 1480, but 1427 is still not resolved as shown below.
Similar to Erroneous admin override message - TOLOGIX - ISLG App Rebuild for Tologix, I am getting an erroneous admin override message without identifying who is currently "editing" the document when there is nobody actually editing the document. Any admin override message should now identify the person who is editing the document, but the message does not contain that information.
Please include it in the next sprint.
Thanks,
Paul
Can you investigate and add as an unplanned item if necessary?
Thanks,
-Martin
This task is done on staging.islg. Now, Any admin user will close the browser or tab directly then admin user is automatically logout for that particular document.
You can check on staging.islg and give your feedback.
When the next HTML comes back, could you try to upload it on staging.islg to test this? Please continue to assign the final step "Publish" to
Thanks,
Paul
I uploaded the HTML for IC/0565/11 on staging.islg. I assigned the final step to Nafiseh as you requested above.
Thanks,
Irit
The issue is resolved on staging.islg, thanks.
Paul
I see this was DevOps #1370 which was deployed to production as in DevOps #1387. However, as shown in the video below, this is not resolved on app.islg
Thanks,
Paul
We have resolved this task on both app.islg and staging.islg. Please check again and confirm.
Cc :
Could you remind me to test this when you upload an XML onto app.islg?
Thanks,
Paul
I uploaded the HTML for IC/0254/11 on app.islg. I assigned the final step to Nafiseh as you requested above in this thread.
Thanks,
Irit
As shown in the video below, the problem is not resolved.
There are two issues to be addressed.
1. After HTML is uploaded and any of the 6 tasks is assigned, it should not trigger an admin override unless somebody is actually editing the document.
2. An admin override message should identify who the person editing the specific document is. As shown below, it simply says "another user." It should identify the name of the person who is supposedly editing.
Thanks,
Paul
This change was revert back as there was an issue on Tuesday. Today, We again newly uploaded this change on app.islg.
As per your above comment, there is no need of second change. because once admin use close the browser window /tab/logout from admin then that message will be disappear.
It means no one is working on that document.
Please check again and let us know the feedback.
Cc :
Could you let me know when you upload an HTML file the next time for me to test this?
Thanks,
Paul
I uploaded the HTML for SC/0015/107 on app.islg. I assigned the final step to Nafiseh as you requested above in this thread.
Thanks,
Irit
Paul
As you see below, there is a regression issue with the erroneous admin override message (without identifying who the editing admin user is) still appearing. As far as I know, nobody is working on UN/0133/28, and Eleo may not have exited the document properly. How can we actually resolve this issue?
Thanks,
Paul
Did you just encounter this issue in the past 15 minutes?
--Martin
CC:
Yes, the video was recorded about 15 minutes ago.
I have been experiencing getting kicked out of the admin dispute document page for days, but I haven't been able to record it to show what triggers the problem. I still got logged out right before I recorded the video above this morning.
Thanks,
Paul
For now, we are using a page that is a bit older, but more stable.
--Martin
DevOps 1427 is marked done. Should we change the status or create a new item?
Paul
This is supposedly deployed via DevOps 1480, but 1427 is still not resolved as shown below.
Please address it as soon as possible.
Thanks,
Paul
Please use https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/1525 to track your progress as the prior task is assigned to the prior sprint.
Thanks,
-Martin