The Flosum Trial Experience
Deployments (also known as releases) allow developers to deploy the relevant changes to the target organization. While Flosum's Deployments are similar to Changesets in Git, they are much easier & powerful to use. Below are some of the features that separate Flosum Deployments from Git's Changesets:
Deploys all metadata components at once
With changesets, developers cannot deploy all the components of various metadata types together. For example, if you are deploying custom settings and a Visualforce page which leverages those custom settings, you cannot deploy all those components at once. You will first need to deploy custom settings and then create a changeset for deploying the Visualforce page. Flosum's deployment feature allows all metadata components to be specified in one composite deployment that can be executed in one click.
Allows multiple developers to combine their changes into one Flosum deployment
Most enterprise organizations have hundreds, if not thousands, of changesets. This makes it hard to track them. Flosum allows developers to combine their changes with other developer’s changes so they can all be deployed at once.
One deployment can be used multiple times
Developers need to create changesets over and over again. For example, if a developer needs to deploy the code from Dev to QA and then again from Dev to UAT organizations, s/he would have to create the changesets twice to move the changes across these two organizations. With Flosum, the same deployment can be reused multiple times to deploy to orgs across the delivery chain.
Can deploy all types of metadata components
Salesforce changesets do not support all types of metadata components. If you need to deploy certain types of metadata components, you would have to deploy them manually or by using an IDE such as Eclipse.
Promotes code easily between orgs with the click of a button!
Migrating the code between teams and other orgs does not have to be painful. Developers do not have to use changesets, build-scripts or resolve dependencies manually. Flosum automates the entire code at the click of a button.
Now, You Try It!
Creating A Deployment
- In the "Branches" Tab select, your "Integration Branch 1"
- Push the "Add to Deployment" button at the top right of the screen
- In the "Deployment Name" box that appears, enter the name "Deployment 1"
- Utilize the blue checkbox below to select all of the components
- Click "Transfer to Deployment" at the right of the screen.
Congratulations, your deployment has been created! Next, you can validate the deployment, and Flosum will check the deployment against the target org to see if it will be successful.
Validate A Deployment
- With your newly created deployment open, click "Validate" at the top of the screen.
- Select your Target Organization from the dropdown list.
- In the run test box, you can select which tests you would like to run. For trial purpose, select "Default"
- Click on "Validate" at the top right of the screen. This may take a couple of minutes.
- You will be directed to the validation screen and under the details tab, you'll see the details of Deployment 1 listed. Scroll down to see the "Succeed?" box. If this box is checked, your deployment will be successful.
- To view the validation success log, or validation error log, click the "Related tab at the top of the screen"
- On the next page, click "View Details" and then select the file you wish to view. Depending on your results, this will be the "validate success log" or the "validate error log"
- Once your deployment has successfully passed the validation test, it can be deployed by selecting the "Deploy" button in the deployment tab.
Way to go!! You've successfully completed a deployment and should now have a good understanding of the basic features of Flosum. However, there's so much more! To take a look at a few more of our features, continue to our bonus steps 7-10.