What do you need help with?

Getting Started With Deployments



Deployments: An Overview

Deployments are synonymous with releases. Deployments are also like Changesets, without the problems of Changesets. With deployments, we can deploy the relevant changes to the target organization.

At the heart of each deployment is a powerful manifest which enlists all the components that will be deployed. Just tell Flosum the components to be deployed, and Flosum will take care of the rest. The entire release can be now deployed with one composite deployment!

Deployments resolve many of these existing challenges:

Deploy all the metadata components in one shot
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 deployed in one click.

Allow 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 Changesets

Create once and deploy 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, he or she 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.

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.

Promote 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 and do not have to resolve dependencies manually. Flosum automates the entire code at the click of a button.


Creating a Deployment using a Snapshot:

  1. Click on the Deployments tab.
  2. Click on New (to create a new deployment).
  3. Select the Source Organization name.
  4. Select the Snapshot that was just created.
  5. Enter the Deployment name
  6. Search for the metadata components that you want to deploy (in this case, select the Visualforce page and CustomObject created).
  7. Click on Add to Deployment.
  8. Voila! You just created a new deployment from your snapshots.

Now, let's deploy

  1. Go to the Deployments tab.
  2. Select your deployment name.
  3. Click on Deploy
  4. Select the Target Salesforce Organization that you want to deploy to
  5. Select Run Test option as Do not run any tests
  6. Click on Deploy
  7. Please do not close the browser window till the deployment completes.
  8. As soon as the deployment completes, Flosum will show the deployment logs.

Observe: In the attachments section, you will see Success Log and Error Log. The success logs shows the components which have been created, updated or deployed (without any change). The error logs shows the components which could not be deployed. For each failure, it shows all the failures.

You have done your first deployment with a just a few clicks!

Optional: You can modify the same deployment and deploy it again. Add or remove components from the manifest, and deploy it again. You can deploy it to the same organization or deploy it to any other organization.

Congratulations! You have deployed your first change with Flosum.

Print Friendly and PDF
Was this article helpful?
0 out of 0 found this helpful