Salesforce - How to Deploy between Environments (S

2020-05-20 08:14发布

We're looking into setting up a proper deployment process.

From what I've read there seems to be 4 methods of doing this.

  1. Copy & Paste -- We don't want to do this
  2. Using the "Package" mechanism built into the Salesforce Web Interface
  3. Eclipse Force IDE "Deploy to Server" option
  4. Ant Script (haven't tried this one yet)

Does anyone have advice on the limitation of the various methods .

Can you include everything in a Web Interface package?

We're looking to deploy the following items:

  • Apex Classes

  • Apex Triggers

  • WorkFlows

  • Email Templates

  • MailMerge Templates -- Can't seem to find these in Eclipse

  • Custom Fields

  • Page Layout

  • RecordTypes (can't seem to find these in Website or Eclipse)

  • PickList items?

  • SControls

7条回答
孤傲高冷的网名
2楼-- · 2020-05-20 08:55

From the docs:

A package must be managed for it to be published publicly on AppExchange, and for it to support upgrades. An organization can create a single managed package that can be downloaded and installed by many different organizations. They differ from unmanaged packages in that some components are locked, allowing the managed package to be upgraded later. Unmanaged packages do not include locked components and cannot be upgraded. In addition, managed packages obfuscate certain components (like Apex) on subscribing organizations, so as to protect the intellectual property of the developer.

Advantage to managed package would be that it allows you to easily version and distribute things across multiple SFDC organizations.

查看更多
登录 后发表回答