Source Control in SAP Build Apps
If you are a developer, you are probably familiar with the concept of source control. Yet, for those who are new to the area, source control is a crucial tool that allows engineers to track changes to their projects over time. Furthermore, it enables seamless collaboration on projects, implements the ability to track changes, and undo them as needed.
Collaboration: It can be difficult to work on a project with other developers without a unified change history. Source control allows you to have a single point of truth when developing as a team.
Organization: Your project may expand and become complex as it develops. Source control allows you to keep version backups that can be enabled at any point in the future.
In the image below, you can find an example of a History entry. The oldest entry marks the point of creating a data resources called “On-Device”. Afterward, a page called “Page 2” was created. The last two entries represent a change in the UI canvas and Logic canvas.
Every change is accompanied by a page identifier in the beginning. Thus, an entry titled ‘Page 2 logic, Page 2 UI’ shall be interpreted as User Interface modification on a page named ‘Page 2’.
Visual cloud functions are also enabled with the History feature. Read more about this here.
Apart from having the ability to rollback to previous versions, source control enables you to share the development with others. In the SAP Build Lobby, you can use the three-dot menu to manage members of your project, or simply click on the Members list column.
There are three user roles available:
- Viewer: Read-only actions – Inspecting the app and history.
- Developer: Edit, deploy, release – Makes changes to the application
- Administrator: Complete access, including editing, sharing, and deleting a project – Full source control of the project.
Read more about project sharing here.
Export – Import
Export – Import enables source accessibility for your project. By simply exporting your app in SAP Build Lobby, you can transfer the source file between BTP subaccounts or simply share it with your colleagues.
Upon receiving an export file, they can seemingly import it via Lobby:
Export – import becomes particularly handy in case your project needs to go through several stages of testing and quality assurance. Developers can export their applications and share them with the quality engineers, allowing both to separate their workflows without intervening with each other.
Read more about export – import here.
The newest Source Control feature that can be found in SAP Build Apps is ‘Replace’:
Replace allows you to override all content of an application with a provided backup file. Backup files can be generated using the ‘Export’ button, above.
This feature is incredibly useful for making application fall back points. Simply export your app and rename the file to have a distinct version and/or timestamp. With that, you can always replace the content of any app with the saved version.
I hope I was able to highlight the benefits of using source control in your development workflow. From enabling easy collaboration and organization to providing a history of changes and the ability to roll back if necessary, source control is an essential tool for any development team. I strongly recommend checking out the new ‘Replace’ functionality, that is useful for making large-scale changes to the project.
Whether you’re working on a small project or a large one, source control can help improve your workflow and ensure the success of your projects.