Maintain Your Dev Lifecycle and Deployment Designer Certification for Spring '19
After completing this unit, you’ll be able to:
- Describe key features available in Development Lifecycle and Deployment Design as of Spring ’19.
If you hold the Salesforce Development Lifecycle and Deployment Designer credential, keep in mind that you need to complete this module by the due date to maintain your certification. Another important part of maintaining your credential is ensuring your Trailhead and Webassessor accounts are linked.
Interested in learning more about getting certified? Check out the Salesforce Development Lifecycle and Deployment Designer credential.
Salesforce introduced a ton of great feature enhancements. Let’s take a look at some of the more important ones for this release.
The Salesforce Certified Development Lifecycle and Deployment Designer has experience analyzing the environment and requirements to design an appropriate governance framework and to manage the development and deployment lifecycle on the Lightning Platform. The designer has experience designing and implementing complex development and deployment strategies, as well as communicating the proposed solution and design trade-offs to business and technical stakeholders alike.
You can choose to deploy processes and flows as part of a continuous integration and continuous delivery model without manually activating them. Previously, processes and flows were always deployed as inactive. In production orgs, a new setting lets you deploy a new active version of a process or flow via change sets or Metadata API. This setting doesn't appear in non-production orgs (such as scratch, sandbox, and developer orgs), because you can always deploy a new active version.
This change applies to Lightning Experience and Salesforce Classic in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.
A process or flow template is a base business process that you can clone to create customized business processes. Unlike non-template processes and flows, if you install a template from a managed package, you can open and clone it. Even if you build your own templates and don’t use managed packages, marking a process or flow as a template clearly identifies it as a base business process.
Although you can activate templates and have them run just like other processes and flows, templates are typically kept inactive. After you clone a template and customize the clone, activate the clone in your org. If you install a template from a managed package and later install an upgrade, your template is overwritten with the updated version, but your clones aren’t affected.
Sandbox cloning simplifies the management of multiple concurrent work streams in your application lifecycle. Clone an existing sandbox for each type of work, such as development, testing, and staging. As you move from one development stage to the next, clone an existing sandbox rather than using your production org as the source. This pattern simplifies the customization of individual sandboxes. Your colleagues can easily clone individual sandboxes instead of sharing one sandbox to avoid stepping on each other’s toes.
This change applies to Lightning Experience and Salesforce Classic in Professional, Enterprise, Performance, and Unlimited editions.
As you start creating more unlocked packages, you might need to refactor your package and move metadata from one unlocked package to another unlocked package. You can now deprecate metadata in an unlocked package, move that metadata to a new package, and then install the new package in your production org. Upon successful installation of the new package, the deprecated metadata becomes associated with the new package. This feature simplifies that process.
This change applies to Lightning Experience, Salesforce Classic, and all versions of the Salesforce app in Group, Professional, Enterprise, Performance, Unlimited, and Developer editions.
In addition to the changes we’ve made in weekly releases, Salesforce Extensions for VS Code v45 includes some major enhancements. Accelerate Lightning web component development with the VS Code Lightning Web Components extension, which is now included in the Salesforce Extension Pack. Start preparing now for the October 2019 retirement of Force.com IDE.
For information about enhancements made in weekly releases, see the Salesforce Extensions for VS Code change log.
Simplify Lightning Web Component Development with the VS Code Extension Pack
Install the Salesforce Extensions for VS Code extension pack, and get the Lightning Web Component extension to speed your component development. You no longer need to install or manage separate extensions or worry about the order in which you install and update your Salesforce extensions.
Force.com IDE Is Being Retired in October 2019
The Force.com IDE plug-in for Eclipse is in a maintenance-only state. We will still provide support through our official channels for the product until its retirement date on October 12, 2019, but the only updates will be for critical security issues that arise before the retirement date.