Learn What’s New with Development Lifecycles for Winter ’24
Learning Objectives
After completing this unit, you’ll be able to:
- Manage and release changes with DevOps Center.
- Select who has access to a sandbox.
- Transfer package ownership to a different Dev Hub.
Salesforce Certification
If you hold a Salesforce Architect certification, keep in mind that you need to complete this unit and the other 4 units in this module by the due date to maintain your certification. Another important part of maintaining your certification is ensuring your Trailhead and Webassessor accounts are linked.
Interested in learning more about getting certified? Check out all the Salesforce Architect certifications.
Manage and Release Changes with DevOps Center
Manage your changes and releases using the DevOps Center point-and-click interface, or directly from the source control system, or a combination of both. In the background, we manage the source control branches so developers and builders can focus on development tasks.
Where: This change applies to Lightning Experience in:
- Developer, Professional, Enterprise, Performance, and Unlimited Editions.
- Government Cloud Plus. Turning on DevOps Center in Government Cloud Plus orgs can send data outside the authorization boundary. Contact your Salesforce account executive for more details.
Who: DevOps Center is available to all customers and can be enabled from the Setup menu. To use DevOps Center, add team members as users in the org in which DevOps Center is installed. Users also require a GitHub account and access to their team’s GitHub repository.
Why: Unlike change sets, where you manually track your changes, changes are captured in a source control system. Say goodbye to spreadsheets. You have a single source of truth for configuration and code, which improves collaboration across all functions: admins, developers, release managers, QA, and other business stakeholders.
How: Enable DevOps Center in the org in which you plan to install DevOps Center, accept the license agreement, and then install the managed package. From Setup, enter DevOps Center
in the Quick Find box, then select DevOps Center.
If you’re currently using the DevOps Center beta, we’ll push the upgrade to your org automatically. However, if you don’t want to wait, you can go ahead and install it immediately from the DevOps Center Setup page.
Select Who Has Access to a Sandbox
Selective Sandbox Access helps you limit access to a sandbox to only required users when refreshing or creating a sandbox. By default, all active users in the source org have access to the sandbox, but only the user who creates the sandbox has their email address in the original format (without .invalid
appended to it).
With selective access, a Salesforce admin grants access to specific users through a public group. The email addresses for the users included in the group remain in their original format and don’t need to be modified. Users who aren’t part of the public group have to be unfrozen in the sandbox in order to access it.
Where: This change applies to sandboxes of Professional, Enterprise, Performance, Unlimited, and Database.com editions.
When: This feature is available in production orgs when they’re upgraded to the Winter ’24 release starting in mid-October 2023. Update: The release of this feature is delayed.
Who: All users in the production org with the Manage Sandbox user permission.
Transfer Package Ownership to a Different Dev Hub
Ownership transfer of an unlocked package or second-generation managed package (managed 2GP) from one Dev Hub org to another is generally available. A transfer can occur internally between two Dev Hub orgs that you own, or you can transfer a package externally to another Salesforce customer, Salesforce Partner, or ISV. This change provides a way to sell an unlocked or second-generation managed package.
Where: This change applies to unlocked packages and second-generation managed packages.
How: To initiate a package transfer, log a case with either Salesforce Partner Support or Salesforce Customer Support. Because this procedure is complex, Salesforce performs the package transfer process for you.
For security reasons, package transfers between a Dev Hub located in Government Cloud and a Dev Hub located outside Government Cloud aren’t permitted.
For second-generation managed packages, package transfers are only available for packages that have passed AppExchange security review. If your managed 2GP package hasn’t passed security review, consider creating a new managed 2GP using your preferred Dev Hub.
Resources
- Salesforce Help: Manage and Release Changes with DevOps Center
- Salesforce Help: Select Who Has Access to a Sandbox
- Salesforce Help: Transfer Package Ownership to a Different Dev Hub