Skip to main content
The Salesforce plugin provides an integration layer between FlexDeploy and Salesforce for building and deploying Salesforce objects. It can source package-based builds from an SCM, or from Salesforce org.
Check Salesforce Tutorial to Configure and start using for Salesforce deployments.Check the Data Deployments Tutorial to start using for Salesforce data deployments.
The domains/IP addresses should be whitelisted/allowed in your firewall configuration on your FlexDeploy server to ensure the proper functioning of the plugin

​
Supported Versions

  • Java 8+ must be used on the endpoint
  • The SCM Git is integrated into key Salesforce comparison features. Using other SCMs limits the available feature set.
  • See FlexDeploy Salesforce Version Matrix for information about what Salesforce API levels you can target with which versions of FlexDeploy.

​
Key Features

  • Supports No-Code, Low-Code, pro programming, and hybrid App Development models.
  • Supports Data Deployments
  • Supports the package-based Deployment model where changes made in Salesforce Orgs are synced without requiring an SCM.
  • Supports the package-based Deployment model where changes are checked into SCM, worked on there, and later deployed to different environments.
  • Supports deploying partial objects (subcomponents) for Profiles, Custom Objects, etc.
  • Allows for back up before deployment, ensuring a smooth rollback if necessary. See Build & Deploy Projects for details on performing deployment rollback.
  • Allows adding multiple account codes to a single environment. This allows updating multiple sandboxes in a single deployment. Automatic rollback is not available when deploying across multiple accounts. During deployment, files for each account are stored in a backup repository, and any rollback must be carried out manually using these backups.
  • Recognizes AI Authoring Bundle (AiAuthoringBundle, directory aiAuthoringBundles) and API Named Query (ApiNamedQuery, directory apiNamedQueries, file suffix apiNamedQuery) metadata so those files are identified and included during package creation and deployment. These types were introduced in Salesforce API 65.0. @Since 11.2.0.0

​
Plugin Operations