Here you will find videos about how to work collaboratively using GeneXus and GeneXus Server.
This is just an overview. For further information, please check GeneXus Server.
Consider a development team of two developers. At the beginning of the project, one developer creates a local New Knowledge Base and sends it to the server by selecting File > Send Knowledge Base to GeneXus Server.
The other member of the development team starts to work by creating a local Knowledge Base from GeneXus Server. To do so, he selects File > New > Knowledge Base From GeneXus Server.
Watch: How to send a Knowledge Base to GeneXus Server
Watch: How to connect to a Knowledge Base in GeneXus Server
How does it work?
Each developer works on a personal Knowledge Base (their own copy). At this time no connection is required and there is no interaction with the other developers.
When a developer decides that a feature is complete and has to be shared with the rest of the team (that is to say, added to the full solution) they must Commit these changes.
Watch: How to send my changes to the Server
When a developer executes a Commit operation, the changes made to their personal Knowledge Base (that is, changes, additions, and deletions of objects) are sent to GeneXus Server. In GeneXus Server, this knowledge is consolidated with the existing knowledge and feedback about this operation is given to the developer doing the Commit.
The Update operation is somewhat the opposite of a Commit. It applies all changes committed by other developers to the developer’s personal Knowledge Base.
Watch: How to receive changes made by other developers in the server
- This is just a simple sample. The same concept applies to larger development groups and KBs. Also, one developer is enough to use GeneXus Server and enjoy its benefits.
- You can watch more videos about GeneXus Server at Team Development videos.