I had some problems with rules that got overriden when my teammates uploaded a new version of their rules in the same project i'm working on. Whats the best way to avoid it? whats the common way to have many people working on same projects in OpenL? if i change one rule, and my teammate change another rule. When we both click Save button, will we lose any one of these rules?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Typically we don't work in WebStudio, and edit the XLS directly and upload. We're working in 5.21.12 and no locks are applied, so we have to keep in constant contact if we work on the same project.
In most cases, we have to divide work by the module to prevent having to manually merge changes. When we save a change, we have to notify the other person so they can open the Repository tab and open the latest revision before uploading their module. Otherwise, the revision they have in their workspace will be old, and revert your changes.
I'm hoping the mentions of Git in the new properties files mean that we'll soon be able to leverage it for version control.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Robert and eb,
Could you please provide a detailed step-by-step scenario, in what cases you faced with overwriting issue? We are working on improving a user experience for multy-user mode and fixing some known issues, so we would like to take into account your cases too.
For now the best advice would be 1) Make sure, that the project version you going to edit is the latest. 2) Make a little change in the project via webstudio to lock it, so other users could not edit it, and then continue to edit a project the way you got used to.
Best Regards,
Alena.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
User1 exports the newest revision (1) of Project 1, Module A and begins work
User2 opens Webstudio, goes to Repository.
User2 exports the newest revision (1) of Project 1, Module B and begins work
User1 edits Module A XLS
User1 opens the Repository tab, Selects Project 1, checks its Properties tab Revision number to ensure their editor still has the latest version.
User1 selects Module A in the left nav, and clicks "Update file" OR User1 goes to Editor, Module A, and clicks "Update" (revision is now 2)
User2 edits Module B XLS
User2 opens the Repository tab, Selects Project 1, checks its Properties tab Revision number (revision 2 is now listed) to ensure their editor still has the latest version (they did not note the opened revision. the "Modified At" date did not change as changes were applied in the same day, and did not bother to check if "Modified By" was not them.).
User2 selects Module B in the left nav, and clicks "Update file" OR User2 goes to Editor, Module B, and clicks "Update" (revision is now 3)
Module A's changes are lost as User2 actually still had revision 1 loaded in the editor despite revision 2 being shown in the Repository's Properties tab.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello eb,
I managed to reproduce this issue on Openl 5.21.12, but failed to reproduce on 5.12.13.
It's looks like this issue was fixed together with existing issue EPBDS-8133 Project doesn't change it's status to "Locked" for user2, if user 1 exported a module, update it and upload back
Now in case when user2 clicks "Upload" button, expected behaviour would be notification message "You are trying to edit old revision of the project. Do you want to overwrite newer revision?".
Beest Regards,
Alena.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've mentioned internal ticket number which his not accessible and published outside the project. Unfortunately, It may confuse you, sorry for that.
But there is a list of public issues on github https://github.com/openl-tablets/openl-tablets/issues
Best Regards,
Alena.
Last edit: OpenL Tablets 2019-05-04
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I had some problems with rules that got overriden when my teammates uploaded a new version of their rules in the same project i'm working on. Whats the best way to avoid it? whats the common way to have many people working on same projects in OpenL? if i change one rule, and my teammate change another rule. When we both click Save button, will we lose any one of these rules?
Typically we don't work in WebStudio, and edit the XLS directly and upload. We're working in 5.21.12 and no locks are applied, so we have to keep in constant contact if we work on the same project.
In most cases, we have to divide work by the module to prevent having to manually merge changes. When we save a change, we have to notify the other person so they can open the Repository tab and open the latest revision before uploading their module. Otherwise, the revision they have in their workspace will be old, and revert your changes.
I'm hoping the mentions of Git in the new properties files mean that we'll soon be able to leverage it for version control.
Hello Robert and eb,
Could you please provide a detailed step-by-step scenario, in what cases you faced with overwriting issue? We are working on improving a user experience for multy-user mode and fixing some known issues, so we would like to take into account your cases too.
For now the best advice would be 1) Make sure, that the project version you going to edit is the latest. 2) Make a little change in the project via webstudio to lock it, so other users could not edit it, and then continue to edit a project the way you got used to.
Best Regards,
Alena.
Our simple two user scenario:
Module A's changes are lost as User2 actually still had revision 1 loaded in the editor despite revision 2 being shown in the Repository's Properties tab.
Hello eb,
I managed to reproduce this issue on Openl 5.21.12, but failed to reproduce on 5.12.13.
It's looks like this issue was fixed together with existing issue EPBDS-8133 Project doesn't change it's status to "Locked" for user2, if user 1 exported a module, update it and upload back
Now in case when user2 clicks "Upload" button, expected behaviour would be notification message "You are trying to edit old revision of the project. Do you want to overwrite newer revision?".
Beest Regards,
Alena.
Thank you for stepping through this and confirming! That fix will be a great help.
There isn't a publically accessible list of issues by chance is there (as you mention EPBDS-8133)?
Hello,
I've mentioned internal ticket number which his not accessible and published outside the project. Unfortunately, It may confuse you, sorry for that.
But there is a list of public issues on github
https://github.com/openl-tablets/openl-tablets/issues
Best Regards,
Alena.
Last edit: OpenL Tablets 2019-05-04