Flosum is a flexible and powerful application built entirely on the Salesforce platform. This article explains the entire application development process in Flosum from ideation of a new feature to its deployment into production. The application development process can be constructed in many different ways, and the following is just one example of how Flosum can improve your workflow.
For the purpose of this article, the term “developer sandbox” is used to refer to a developer sandbox or to a scratch org created using Salesforce DX.
1. Set up the Developer Sandbox
Developers can download the latest code from the repository or the master branch into the development sandbox in order to hit the ground running. This article explains on the process of syncing developer sandboxes with the repository.
2. Populate Developer Sandbox With Seed Data
If the developer sandbox was refreshed or a new scratch org was created, developers can populate those environments with seed data. This article shows how developer sandboxes can be populated with seed data in a single click.
3. Make Changes and Push Them up
Once feature changes have been made in a developer sandbox, they can easily be pushed directly into the Flosum org. In this process, the changes from the developer sandbox are committed into a feature branch.
4. Code Review, Code Scans, and Test Automation
Depending on your configuration, Flosum can automatically begin testing the code as follows:
If static code analysis is configured, Flosum will automatically start scanning the newly committed code.
If the regression testing framework is configured, test execution will begin before the code is handed off to the QA team. Girish to embed the links.
5. Create a Release Train and Merge the Feature Branches
If continuous integration is set up, feature branches can me merged with release branches and then be automatically deployed to various orgs as defined in the pipeline. Alternatively, feature branches can be merged into a common integration or release branch so they can be manually deployed to higher environments after review and approval.
If configured, the code coverage will be automatically initiated after the new code is created.
6. Regression Testing
7. Business Approvals
8. Deploy to Production Orgs
The above steps are meant to show only a high-level, abstract example of the Flosum process. Depending on your branching, sandbox, and hand-off strategy, the complete functionality of Flosum gives you the power and flexibility to serve the diverse needs of your customers.