Hi

How does a developer work on a change without impacting others work and integrate his work seamlessly with other developers once completed.

Thank you

Hi,


Why do you ask this?

How do you think it should be handled?

How do you do this currently in Outsystems and why does it not work?

Can you even think of a non-it solutions how they do this?


Puja Rani wrote:

Hi

How does a developer work on a change without impacting others work and integrate his work seamlessly with other developers once completed.

Thank you

Hi Puja,

This is a very broad topic so don't expect any complete answers. There is an hefty amount of material about this on the learn section of outsystems.com and there is also plenty of documentation.

But to go into your questions;

  1. How does a developer work on a change without impacting others work?
    This can be achieved in a multitude of ways but let's start with good architecture. By making sure that the different components are in their correct architectural section and split in logical modules you can prevent development collisions and merge conflicts. You can also prevent a great impact on other teams by first agreeing on the used API's for the consumable or produced Actions and Screens. By not needing to change the API a lot you will not break any underlying code as quickly. 
  2. How does one seamlessly integrate it's work?
    By using the One-Click publish button. This will merge your work into the already published application. Any merge conflicts will be identified and need to be fixed before the publish will continued.

If you are expecting Git like features with branching and such then you will be disappointed. OutSystems doesn't have that.