I have a situation where one team of developers is working on an espace while another wants to do a project with the same espace. In "normal" development processes I would branch the code and give each developer/team their own edition while later these branches can be merged. This is very hard to do in the OutSystems way of working. What do you usually do in these situations and are there any plans to introduce branching in OutSystems?
Hi Smriti,
As for your last question, no, OutSystems is not planning to implement branching.
That said, if two teams need to access the same module, for a longer time, then you either have an ownership problem, or the module is just way too big and encompasses more than one functionality.
In general, a single module should not be needed to be worked on by two teams, let alone for a prolonged period of time. As Sandeep wrote, you can use the merge feature to merge smaller changes. But if you need two teams working on the module for substantial changes, it's perhaps time to split the module into two or more.
Hi Smiti,
The best practice is to create ownership on Applications, and that an Application can only be changed by one team.
see https://success.outsystems.com/Documentation/Best_Practices/Architecture/OutSystems_Domain_Driven_Architecture/Domain_Driven_Design_with_OutSystems
Another option is to combine teams.
Hans
Hi,
Multiple developer can work on same application and same module. OutSystems have feature merge and publish.
If multiple developer publish code then Outsystems show popup with code diff information and user can select own code or another code in pop and publish to server.
Multiple developer can't work logic , block , screen or widget at same time .
Regards,
Sandeep Mallah
We can manage our team from the user management where we assign the multiple developer to multiple app but when we talk about team app is didn't assign to multiple team.
Thanks
Narendra Tiwari