Development Lifecycle 13% Flashcards
What is the Force.com migration tool?
A Java/ANT-based command line utility for moving metadata between a local directory and a SFDC organization.
True/False: The following scenario can be done using the Force.com migration tool?
You want to change the contents of a file between organisations - I.E. retrieve a file from Org. A, make a change, and then deploy to Org B.
True.
Note, not possible with the Force.com IDE, as you would need to save the change to Org A, before deploying to Org. B.
True/False: The Force.com migration tool is not useful for development projects where you need to populate a test environment with lots of data,
False.
Note, making changes with an automated script is far faster than entering them by hand.
True/False: The Force.com migration tool can be utilized in Multi-stage release processes? - I.E. iterative building, testing, staging, deployment.
True.
Note, Scripted retrieval and deployment of components can make the process much more efficient.
True/False: The Force.com migration tool can be used with advantage in the following scenarios:
- Populating a test environment with data
- Change contents of files between organisations
- Multi-stage release processes
- Repetitive deployments using the same parameters
- Migrating from staging to production
True.
What is the Bulk API?
A RESTful API that is optimal for loading or deleting large sets of data.
Note, used to query, insert, update, upsert, or delete a large number of records asynchronously by submitting batches that Salesforce processes in the background.
What is the Metadata API
The Metadata API is used to retrieve, deploy, create, update or delete customization information, such as custom object definitions and page layouts.
Note, this API is intended for managing customizations and for building tools that can manage the metadata model, not the data itself.
True/False: To create, retrieve, update or delete records, such as accounts or leads, use the Metadata API.
False.
Note, to change data use data SOAP, REST or BULK API.
Order the following to get a typical development lifecycle:
- Develop
- Create testing environments (incl. UAT & Integration)
- Create development environments
- Test
- Schedule release
- Migrate changes from UAT environment to staging
- Perform UAT
- Migrate changes from integration environment to UAT
- Migrate changes from development environment to integration
- Replicate production changes
- Create development environments
- Develop
- Create testing environments (incl. UAT & Integration)
- Migrate changes from development environment to integration
- Test
- Migrate changes from integration environment to UAT
- Perform UAT
- Migrate changes from UAT environment to staging
- Replicate production changes
- Schedule release
List the three types of Sandboxes and the difference between them.
- Partial Copy Sandbox - Metadata
- Developer Sandbox - Metadata and a subset of Data
- Full Sandbox - Metadata and Data
Describe unmanaged packages.
Unmanaged packages are typically used to distribute open-source projects or application templates to provide developers with the basic building blocks for an application.
Once the components are installed from an unmanaged package, the components can be edited in the organization they are installed in.
Note, unmanaged packages should not be used to migrate components from a sandbox to production organization.
Describe managed packages.
Managed packages are typically used by Salesforce partners to distribute and sell applications to customers. Note, these packages must be created from a Developer Edition organization. - Managed packages are also fully upgradeable.
Order the following to get the general procedure when using the Force.com migration tool to copy metadata from one SFDC Org. to another.
- Construct a project manifest in package.xml
- Enter credentials and connection information for the Source Org in build.properties
- Run the tool to deploy metadata files or deletions to SFDC
- Create retrieve targets in build.xml
- Enter credentials and connection information for the Destination Org in build.properties
- Run the tool to retrieve metadata files
- Enter credentials and connection information for the Source Org in build.properties
- Create retrieve targets in build.xml
- Construct a project manifest in package.xml
- Run the tool to retrieve metadata files
- Enter credentials and connection information for the Destination Org in build.properties
- Run the tool to deploy metadata files or deletions to SFDC
True/False: Unmanaged packages can be useful for distributing initial components to multiple organisations
True.
Note, You cannot make further changes to those files using the same method.
Common Metadata Issues: What is the issue around retrieving custom fields on standard objects?
When we use the wildcard symbol in package.xml, to retrieve all objects, we don’t retrieve custom fields on standard objects.
Note, this can instead be set up in the project manifest.