This article provides a high-level overview of the deployment functionality in Flosum. Deployments in Flosum are delivered as patches, and Flosum can deploy all components that are supported by the metadata API as well as the Tooling API.

Flosum can deploy from the following sources:

  • Uncommitted components from branches
  • Committed components from the master branch/repository
  • Components retrieved from any other organization

Creating deployments in Flosum is quick and easy. You can even create a deployment from multiple user stories or commits. The following are just some of Flosum’s features that help to reduce the number of manual steps necessary during the deployment process.

Search and Replace Text Before Deployment: Sometimes you need to directly edit the code in a deployment rather than pulling an entire change back from the development org. Flosum allows you to make these changes to any type of component directly in the deployment without needing to pull back changes that don’t need to be edited.

Environment Variables: Flosum uses environment variables to automatically search and replace text based on the code deployed to various environments.

Deployment of Data: Flosum supports migration of hierarchical data while deploying metadata. The Data Migrator functionality can migrate data for multiple objects at the same time while maintaining the relationships between those objects.

Apex Test Code Execution: During deployment, Flosum can run tests in the following configurations:
Default mode
No Test Run (no apex tests are run unless in a production deployment)
Run Specified Tests (only included apex test classes run; also known as Fast Deploy)
Run Local Tests (runs all apex test classes, excluding managed packages)
Run All Tests In Org (runs all apex test classes, including managed packages)

Approval Process: Because Flosum is built completely on the Salesforce platform, it provides an out-of-the-box workflow approval process to allow developers to easily obtain any necessary approvals.

In addition to approvals, Flosum provides a custom validation framework that allows users to enforce rules and guidelines before changes can be moved to a target organization. This allows development teams to easily enforce a scalable workflow policy.

Impact Analysis: Flosum can show the code differences that will be available on th

Create Fewer Deployments: A deployment can be created in just a few clicks. Once created, you can deploy the same package to multiple orgs instead of re-creating deployments over-and-over again.

Advance deployment concepts such as pick up line and fast apply the paragraph

Rollbacks: Flosum can easily roll back successful deployments. During every deployment, Flosum automatically backs up the code and metadata from the target organization. If you find that the deployment was successful but had undesirable results, you can quickly roll back the entire deployment in a single click. Flosum can also use the back up from a deployment to roll back the code. Because Flosum knows which new components were created, it can automatically remove those components from the target organization.

Regression testing:


Schedule Deployments: Flosum allows you to defer deployments to a later time via the Schedule Deployments functionality. For example, your development team can finish a project during the day, but choose to defer the deployment until off-business hours.

Deployment logs: