4.0 (7 reviews)
Created by
Students also viewed
SITS Introduction
16 terms
Ch. 2 test inspections
42 terms
Terms in this set (95)
The Force.com Migration Tool allows you to migrate metadata between unrelated organizations, so in that sense it's more powerful than change sets. Unlike the Force.com IDE, the Force.com Migration Tool has no graphical user interface. You choose the components you want to deploy, the server address, and other deployment details by editing control files in a text editor and using command-line arguments.
1). Create a development environment.
2). Develop using Salesforce Web and local tools.
3). Create a testing environment.
4). Migrate changes from development environment to testing environment.
5). Test.
6). Replicate production changes in other environments.
7). Deploy what you've developed to your production organization.
2). Develop using Salesforce Web and local tools.
3). Create a testing environment.
4). Migrate changes from development environment to testing environment.
5). Test.
6). Replicate production changes in other environments.
7). Deploy what you've developed to your production organization.
1). Create development environments.
2). Develop using Salesforce Web and local tools.
3). Create testing environments, including UAT and integration.
4). Migrate changes from development environment to integration environment.
5). Test.
6). Migrate changes from integration environment to UAT environment.
7). Perform user-acceptance tests.
8). Migrate changes from UAT environment to staging environment.
9). Replicate production changes in staging environment.
10). Schedule the release.
2). Develop using Salesforce Web and local tools.
3). Create testing environments, including UAT and integration.
4). Migrate changes from development environment to integration environment.
5). Test.
6). Migrate changes from integration environment to UAT environment.
7). Perform user-acceptance tests.
8). Migrate changes from UAT environment to staging environment.
9). Replicate production changes in staging environment.
10). Schedule the release.
--Developer - Developer sandboxes copy customization (metadata), but don't copy production data, into a separate environment for coding and testing.
--Developer Pro - Developer Pro sandboxes copy customization (metadata), but don't copy production data, into a separate environment for coding and testing. Developer Pro has more storage than a Developer sandbox. It includes a number of Developer sandboxes, depending on the edition of your production organization.
--Partial Copy - A Partial Copy sandbox is a Developer sandbox plus the data that you define in a sandbox template.
--Full - Full sandboxes copy your entire production organization and all its data, including standard and custom object records, documents, and attachments. Use the sandbox to code and test changes, and to train your team about the changes. You can refresh a Full sandbox every 29 days.
--Developer Pro - Developer Pro sandboxes copy customization (metadata), but don't copy production data, into a separate environment for coding and testing. Developer Pro has more storage than a Developer sandbox. It includes a number of Developer sandboxes, depending on the edition of your production organization.
--Partial Copy - A Partial Copy sandbox is a Developer sandbox plus the data that you define in a sandbox template.
--Full - Full sandboxes copy your entire production organization and all its data, including standard and custom object records, documents, and attachments. Use the sandbox to code and test changes, and to train your team about the changes. You can refresh a Full sandbox every 29 days.