Author: Enrico Murru Page 2 of 19

This is a contributor post. For any question, please contact me for more details.

Salesforce DevOps is the amalgamation of software development and IT operations. It aims to speed up the development cycle, enabling continuous, high-quality software delivery.

In Salesforce DevOps, sandboxes and scratch orgs are essential as they provide isolated environments for development, testing, and staging without disrupting the production environment.

By facilitating continuous integration, delivery, and collaboration, these tools align with the core principles of DevOps, streamlining the application lifecycle from development to deployment.

Understanding Salesforce DevOps

Salesforce DevOps assists in developing and deploying Salesforce applications. It enables organizations to deliver applications and services rapidly and efficiently.

By promoting collaboration between developers and operations teams, DevOps practices help reduce the time to move from code committed to successfully running production.

Critical Components of Salesforce DevOps

Continuous Integration and Delivery (CI/CD): This is a critical aspect of Salesforce DevOps, where developers frequently commit code to a shared repository, and automated builds and tests are run. Continuous delivery extends this by automatically deploying code to production after it passes tests, ensuring that code is always in a deployable state.
Automation: In Salesforce DevOps, automation eliminates manual efforts, reduces errors, and speeds up processes. It is used in testing, deployment, and monitoring to ensure consistent and error-free operations.
Infrastructure as Code (IaC): This practice involves managing and provisioning computing infrastructure through machine-readable scripts rather than manual processes. It promotes consistency and scalability in the infrastructure.
Monitoring: Monitoring tools track application performance, usage, errors, and other metrics. This data is essential for maintaining system health and for making informed decisions.
Cultural Changes: Salesforce DevOps is not just about tools and technologies; it also involves a cultural shift. This includes breaking down silos between development and operations teams, fostering collaboration, promoting ownership, and encouraging continuous learning and improvement.

Image Source: Salesforce

Process and Workflow in Salesforce DevOps

The Salesforce DevOps process typically involves several stages, each with specific workflows:

Plan: This includes defining the requirements, designing the solution, and planning the work.
Code: Developers use Salesforce’s development tools and environments to code the solution. Code is version-controlled, typically using Git.
Build and Test: Code is built into a release and tested. Automated tests are used to verify that the solution works as expected.
Deploy: The release is deployed to a staging environment for further testing and review. Once approved, it’s deployed to the production environment.
Operate: The application is monitored, and any issues are addressed. User feedback is gathered for future improvements.
Learn and Improve: Data from the operation phase and user feedback are used to learn and improve the application and the development process.

Deep Dive into Salesforce Sandboxes

In Salesforce, a sandbox replicates your production environment for testing and development. It provides a space where developers can safely experiment, build, and test changes without affecting the live application.

4 Types of Sandboxes in Salesforce:

Developer sandboxes: Created explicitly for coding and testing purposes, allowing a single developer to work with a copy of the organization’s configuration without any production data.
Developer Pro: Developer Pro sandboxes are similar to Developer sandboxes but provide more storage. They’re designed to handle more extensive development and testing tasks and accommodate larger teams.
Partial Copy: Contain your organization’s metadata and a sample of your production data. They are used for complex testing and training purposes.
Full: Full sandboxes are a complete copy of your production org, including all data and metadata. They are used for performance testing, load testing, and staging.

How to Use Sandboxes in Salesforce Development

Salesforce Sandboxes are used for development, testing, and training without compromising the data and functionality of the production environment.

Here are the steps to use sandboxes in Salesforce development:

Create or refresh a Sandbox: Based on the requirements, create or refresh a sandbox using (Developer, Developer Pro, Partial Copy, or Full).
Develop and Test: Developers make the necessary changes and additions in the sandbox environment, including creating new features, customizing existing ones, or fixing bugs. Once the changes are made, they can perform unit tests to ensure everything works as expected.
User Acceptance Testing (UAT): After the developer’s testing, the business users or QA team can review and test the changes.
Deploy to Production: After successful UAT, the changes can be deployed to the production environment using change sets, Salesforce CLI, or any third-party CI/CD tool.

Image Source: Salesforce

Benefits and Limitations of Using Sandboxes

There are benefits and limitations to using Sandboxes. Knowing them can help your team utilize them to their full potential:

Benefits	Limitations
Different teams can use multiple sandboxes for simultaneous development and testing.	Keeping Sandboxes synchronized with the production environment can be challenging.
Sandboxes can train users and test real-world scenarios without impacting live data.	The number of available sandboxes depends on your Salesforce edition and the licenses you have.
A safe environment to develop and test changes without affecting the live production environment.	Full and Partial Copy sandboxes have specific refresh intervals (29 days and 5 days, respectively), which can limit their usability in specific scenarios.

In-depth Understanding of Salesforce Scratch Orgs

Salesforce Scratch Orgs are temporary environments that can be fully customized to mirror different Salesforce editions with varying features and preferences. As part of Salesforce DX, Scratch Orgs are source-driven, disposable deployments of Salesforce code and metadata.

Setting up and Configuring Scratch Orgs

Setting up a Scratch Org involves these steps:

Install Salesforce CLI: Salesforce Command Line Interface (CLI) is a powerful tool required to create and manage Scratch Orgs.
Authenticate Dev Hub: You must authenticate with your Dev Hub org before creating a Scratch Org. Dev Hub is the central hub that controls creating and provides services for Scratch Orgs.
Create a Scratch Org: After authentication, you can create a Scratch Org using the “sfdx force:org:create” command.
Push Source to Scratch Org: You then push your source into the Scratch Org using the “sfdx force:source:push” command.

Image Source: Salesforce

Use Cases and Best Practices for Scratch Orgs

Here are a few use cases and best practices:

Feature Development and Testing: Scratch Orgs are perfect for developing and testing a new feature or bug fix. Each developer can have their own Scratch Org to work independently.
Continuous Integration and Continuous Delivery: Scratch Orgs can be used in CI/CD pipelines where automated tests are run in a Scratch Org to ensure code quality.
Source-Driven Development: One best practice with Scratch Orgs is to always pull changes from the Scratch Org to keep the version control system current.
Dispose after use: As Scratch Orgs are temporary, dispose of them after developing or testing to effectively manage the available Scratch Orgs.

Benefits and Limitations of Scratch Orgs

There are benefits and drawbacks to Scratch Orgs that developers must be aware of.

Benefits	Limitations
Scratch Orgs provide isolated environments that can be tailored to match specific development needs.	Scratch Orgs are temporary, and keeping track of changes if they’re not correctly pulled into source control can be a challenge.
They support a source-driven development model	The number of active Scratch Orgs you can have depends on your Salesforce DX edition and licenses.
Scratch Orgs are ideal for automated testing and continuous integration, which promotes rapid, reliable releases.	The shift from org-based to source-driven development with Scratch Orgs can be a steep learning curve for some developers.

Relative Analysis of Sandboxes and Scratch Orgs

The following analysis overviews the similarities and differences between Sandboxes and Scratch Orgs.

Environment for Testing and Development: Sandboxes and Scratch Orgs are isolated environments used for development and testing. They allow developers to create, modify, and test features without affecting the production environment.
Replication of Production Environment: Sandboxes and Scratch Orgs replicate your production environment. They can be configured to mimic different Salesforce editions with different features and preferences.

Differences between Sandboxes and Scratch Orgs

Choosing between these tools can be complex, but knowing the difference can help make your decision.

Sandboxes	Scratch Orgs
Include production data (based on the sandbox type.)	Scratch Orgs are empty environments that don’t contain any data from your production org.
No expiration	Limited lifespan (maximum of 30 days)
Used for multiple stages of development, including development, testing, staging, and training.	A source-driven development model where changes are tracked in a version control system.

Use Cases for Each: When to Use Sandbox v.s Scratch Org

The following cases state which tool best suits a specific task.

Sandbox: Use Sandboxes for tasks that require persistence and longer-term stability. Sandboxes are ideal for final-stage testing, performance testing, user training, and for staging environments for quality assurance. They are also helpful when you need a copy of your production data for development and testing.
Scratch Org: Use Scratch Orgs for short-term tasks, such as developing new features or testing the impact of changes. They are best suited for individual developers or teams following a source-driven development model. They are also suitable for automating unit tests and implementing continuous integration/delivery pipelines.

Role of Sandboxes and Scratch Orgs in Salesforce DevOps

Continuous Integration (CI) regularly merges code changes into a central repository. Both Sandboxes and Scratch Orgs play a critical role in CI. Developers can use Sandboxes or

Scratch Orgs to create and test features before integrating them into the main codebase. Scratch Orgs are particularly useful for CI because they’re easily made, disposed of, and can be aligned to specific user stories or tasks, enabling isolated testing and reducing potential conflicts.

Role in Continuous Delivery and Continuous Deployment

Continuous Delivery and Continuous Deployment extend CI by automating the release of changes to staging or production environments. Sandboxes can serve as staging environments for these releases, allowing final testing and review before deployment to production.

On the other hand, Scratch Orgs can be incorporated into delivery pipelines to automate the creation of temporary environments for testing. This ensures that code is always in a deployable state, reduces the risk of deployment failures, and speeds up the delivery process.

How Sandboxes and Scratch Orgs Enhance Collaboration and Efficiency

Sandboxes and Scratch Orgs promote a collaborative approach to development. Multiple developers can work simultaneously in different Sandboxes or Scratch Orgs without affecting each other’s work.

Scratch Orgs are tied to source control, allowing easy tracking of changes and facilitating collaboration across distributed teams. The ability to quickly set up, test, and dispose of Scratch Orgs boosts efficiency. With their persistence, Sandboxes allow for extended collaboration over longer project timelines.

Impact on Testing and Quality Assurance

Testing and quality assurance is integral to the software development lifecycle. Sandboxes enable developers to test new features in an environment closely mirroring production. The ability to copy production data (in Full and Partial Copy sandboxes) allows for realistic and robust testing.

Scratch Orgs, being fully configurable, can mimic very specific testing scenarios, providing an environment for fine-grained, accurate tests. By utilizing these tools, developers can catch and fix issues early, ultimately enhancing the quality of the application.

Conclusion

In conclusion, Salesforce Sandboxes, and Scratch Orgs are critical assets in the Salesforce development environment, enabling safe, flexible, and efficient application creation, testing, and deployment.

The Salesforce DevOps landscape, enriched with the complexities and ever-expanding features of Sandboxes, Scratch Orgs, and the Salesforce DX framework, offers a rewarding journey for novice and experienced developers.

Understanding and mastering these tools is pivotal in delivering robust, high-quality applications and fostering continuous learning, growth, and impactful contributions within your organization.

[MadeInItaly] SFDX Lens, your italian Debug buddy

By Enrico Murru

On April 12, 2023

In Post

For the #MadeInItaly series where I want to showcase amazing artisanal Italian products from our incredible Italian Ohana, today’s guest post is delivered by Paolo Carrara, software developer, tech enthusiast, scrum master. After a Master’s degree in Software Engineering, he approached Salesforce ecosystem during his early career in a consulting firm and since then he’s been learning, coding, and thinking about new ways to improve his and his team’s work. A huge fan of the Agile movement and an active collaborator of the Italian agile community. You can visit his page (watch out for a hidden easter egg) here.

Many time things don’t go as we planned; we certainly don’t wish so but we must be prepared in such occasions, and when problems happen, there’s one just key factor: time.

That’s why I developed a tool that could help me get to the core problem quicker than whatever I was previously doing.

And that tool is SFDX Lens, a VS Code Extension available for free on the marketplace.

The typical scenario is this: you are happily developing the next new business logic in Salesforce when suddenly you get 3 different issues from 3 different users in your ticketing system, all marked with high priority. Ugh.
Now once you’ve read the ticket to understand what’s the problem you have to switch from your code to your QA environment, go to Setup > Debug Logs > New > compile all the required fields .. oh no! you have just created the 10^th trace flag for the same user that was in debug last week.
Anyway, now you’re ready and can (if possible) replicate the issue, switch back to VS Code and inspect the log

And you have to do it 2 other times.

Or, you can leverage SFDX Lens’s Command SFDX Lens: Debug user from Org. With this command, the extension lets you pick just 3 options:

An Org from the ones configured in your VS Code
An active user to debug
An amount of time from 15, 30 and 60 minutes

That’s it.

The extension will take care of setting a trace flag for that user with the maximum amount of precision allowed for the trace flag (which is more or less FINEST to everything), a process that usually take 1-2 seconds, and then you’re ready to replicate the issue and get the log in VS Code.

>Can you ask your user to replicate the issue himself?

Even better, “let me just activate the extension”, and 2 seconds after there you go, “go ahead”.

>Are you already connected to the QA environment?

Even better, you can skip point 1. With the command SFDX Lens: Debug user which creates a trace flag in the environment you’re connected to.

>Don’t want to search for the command in VSCode?

There’s a neat button for the command SFDX Lens: Debug user just in the activity bar below your code.

You don’t have to worry about trace flag pollution anymore, the extension ensures there will be just one trace flag per user (which is, the minimum required to set a trace flag)

Here’s a demo:

Right, now you have the log in VSCode and it’s a monolith of 7500 rows so.. what’s exactly happening here?

To address this question I often ask myself, I’ve developed a new command, right now in beta : SFDX Lens: Log Analysis (Beta)

This command helps splitting the log into its components, each displayed visually and proportionally to its duration, so now you can focus on a single execution event at a time

This is particularly useful even for performance tuning, now you can see how many times a trigger fires per execution for example.

Here’s a demo:

Everything is made possible through the use of the @salesforce/core package available here: https://github.com/forcedotcom/sfdx-core

Now the circle is complete between getting the debug logs and analyzing them without leaving your IDE.

CloudOps Best Practices for Your Salesforce Environment

By Enrico Murru

On March 30, 2023

In Post

Another guest post by Gilad David Maayan. Gilad is a technology writer who has worked with over 150 technology companies including SAP, Imperva, Samsung NEXT, NetApp and Check Point, producing technical and thought leadership content that elucidates technical solutions for developers and IT leadership. Today he heads Agile SEO, the leading marketing agency in the technology industry.

What Is CloudOps?

CloudOps is the practice of managing and optimizing cloud-based infrastructure and applications to ensure they operate reliably, securely, and efficiently. It involves the use of tools and processes to automate tasks such as provisioning, monitoring, scaling, and backup, which simplifies the management of cloud resources.

CloudOps professionals work to ensure that cloud environments meet business requirements and performance expectations. They collaborate with software development and IT teams to design and implement cloud-based solutions that align with organizational objectives.

CloudOps is critical for organizations looking to leverage the benefits of cloud computing, including scalability, flexibility, and cost savings. By implementing CloudOps, organizations can optimize cloud resources, reduce downtime, and improve overall performance.

The Core Principles of CloudOps

The pillars of CloudOps are a set of guiding principles and best practices that are essential for ensuring efficient and effective cloud operations. These include:

Automation: This is the foundation of CloudOps, enabling the rapid and consistent deployment and management of cloud resources. This includes automating processes such as provisioning, configuration, and scaling.
Monitoring: Visibility and monitoring are critical to ensure the health and performance of cloud resources. This includes monitoring for availability, performance, and security, and responding to issues quickly and proactively.
Cost optimization: Cloud resources can quickly become expensive if not managed properly. CloudOps focuses on optimizing costs by implementing strategies such as resource allocation and usage monitoring, rightsizing, and cost allocation.
Security: Securing the cloud workloads is a top priority for cloud operations. CloudOps professionals ensure that cloud environments are secure by implementing best practices such as identity and access management, network security, and encryption.
DevOps: CloudOps and DevOps are closely related, with CloudOps supporting the development and deployment of applications in the cloud. This involves collaboration between development and operations teams, and the implementation of agile practices to support continuous integration and delivery.

Why Is CloudOps Important in the Salesforce Environment?

CloudOps is important in any environment that uses cloud services, including the Salesforce environment. CloudOps is important in the Salesforce environment for several reasons:

Application performance: CloudOps is important for ensuring that Salesforce applications and services are performing optimally. By monitoring the performance of Salesforce applications, CloudOps teams can identify and address issues that could impact the user experience.
Scalability: Salesforce is a popular customer relationship management (CRM) platform used by organizations of all sizes. As a company grows and adds more customers, the demand on its Salesforce environment can increase. CloudOps teams can help ensure that the Salesforce environment can scale to meet demand, by adding more resources or making other adjustments as needed.
Security: CloudOps teams are responsible for ensuring the security of the Salesforce environment, including monitoring for threats and vulnerabilities, implementing security controls, and ensuring compliance with industry and regulatory standards.
Cost optimization: CloudOps teams can help organizations optimize the cost of their Salesforce environment by identifying ways to reduce costs without impacting performance or security. This can include adjusting resource usage, implementing automation, and leveraging cloud cost optimization tools.

CloudOps Best Practices for Your Salesforce Environment

Implementing CloudOps best practices in a Salesforce environment is important for ensuring optimal performance, scalability, security, and cost optimization. Here are some best practices to consider:

Use automation: Automation is a key component of CloudOps best practices. Automation can help reduce the time and effort required to manage the Salesforce environment, and can help ensure consistency and reliability. Some examples of automation in a Salesforce environment include automated deployments, automated backups, and automated testing.
Monitor performance: Monitoring the performance of the Salesforce environment is important for identifying and addressing issues that could impact the user experience. CloudOps teams can use performance monitoring tools to identify performance bottlenecks and other issues, and take steps to address them. Performance monitoring should include not only the Salesforce application itself, but also the underlying infrastructure, such as the database and network.
Ensure security: Security is a critical component of CloudOps best practices. CloudOps teams should implement security controls, such as access controls, encryption, and multi-factor authentication, to help protect the Salesforce environment from unauthorized access and data breaches. It is also important to monitor for threats and vulnerabilities, and to implement appropriate security measures to mitigate risks.
Optimize costs: Cost optimization is another important consideration in CloudOps. CloudOps teams should work to optimize the cost of the Salesforce environment by identifying ways to reduce costs without impacting performance or security. This can include adjusting resource usage, implementing automation, and leveraging cloud cost optimization tools.
Leverage DevOps practices: DevOps practices, such as continuous integration and continuous deployment, can help improve the speed and agility of Salesforce development and operations. By automating the deployment process and using automated testing, teams can accelerate the delivery of new features and fixes to the Salesforce environment, while reducing the risk of errors and downtime.
Implement disaster recovery: Disaster recovery is a critical component of CloudOps best practices. CloudOps teams should implement a disaster recovery plan for the Salesforce environment to ensure that critical data and applications can be restored in the event of a disaster or outage. This can include backing up data regularly, implementing failover mechanisms, and testing the disaster recovery plan regularly.
Implement change management: Change management is important for ensuring that changes to the Salesforce environment are implemented in a controlled and predictable manner. CloudOps teams should implement a change management process that includes testing, approval, and documentation of changes, to ensure that changes are implemented without causing unexpected issues.

Conclusion

CloudOps best practices are essential for ensuring efficient and effective management of a Salesforce environment. By implementing automation, monitoring performance, ensuring security, optimizing costs, leveraging DevOps, implementing disaster recovery, and implementing change management, organizations can ensure that their Salesforce environment is reliable, scalable, secure, and cost-effective.

CloudOps enables organizations to leverage the benefits of the Salesforce platform while reducing the risk of errors and downtime. By adopting best practices for CloudOps, organizations can improve productivity, enhance customer satisfaction, and gain a competitive advantage.

I present you ChatGPT Pal, Yet another OpenAI Client 🤖

By Enrico Murru

On March 15, 2023

In Post

About 2 weeks ago I asked #ChatGPT to help me to build a browser extension to call OpenAI’s APIs…in about 1.5 hours I packed a working extension, with a save of about 2/3 hours!

After few questions it gave me the whole extension code, comprised of UI interface, options, manifest and stuff.

The code was not working as output but ChatGPT, it needs modifications and enhancements, but it actually helped me delivering in 1/3 of the time…after that, I coded few other hours because I’m a nerd 🤓 and I wanted to make it easy but complete.

I’ve just published the extension on the Chrome Web Store, have a look and let me know what you think on my social channels!

👉 https://organizer.solutions/chatbuddy.html

TrailblazerDX 2023 registration open! 🤓

By Enrico Murru

On December 21, 2022

In Announcement

Are you ready for 2 full immersion days of Salesforce tech learning in beautiful San Francisco? 😮

If you, an admi/dev/architect, are looking for some real epicness, be ready for:

200+ technical sessions
400+ experts from Salesforce, MuleSoft, Slack, and Tableau
Knowledge share from thousands professionals
Parties, fun, parties, and fun

By registering now, you’ll get a $ 400 discount.

👉Click here for more details

Get a glimpse of the awesomeness with this recap of TrailblazerDX 22.

ORGanizer Connector: create your personal Salesforce credentials hub! 🎯

By Enrico Murru

On December 20, 2022

In Announcement

📣 It’s with great pleasure that I’m announcing that ORGanizer Connector has successfully passed the AppExchange security review and ~~it will soon be publicly listed~~ it’s just been publicly listed!

What’s ORGanizer Connector?

ORGanizer Connector is a free AppExchange app that can be freely installed on any org type (production, sandbox or developer edition).

The app usage is really simple:

manually create Backup records that contains one or more credentials (Backup Items) whose secrets (password and token) are encrypted with a key stored in the main Backup record (which only who has access to the record can get)

massively import ORGanizer for Salesforce backups to automatically create Backup records using ORGanizer for Salesforce backup files

Each Backup can be shared using Salesforce standard sharing model, so org users can see only the record they are allowed to access and nothing more (we suggest a Private sharing model extended with sharing rules or manual sharing)
The package exposes a couple of REST APIs to let external applications integrate
- By having access to a Backup record, you can use the Send Secret by Email button to receive the encryption secret by mail: this secret will be used to decrypt the secrets using the Reveal Password & Token button on the Backup Item record or using the ORGanizer for Salesforce native integration (for Full PRO and Team users only), or creating your own integration following the Github repo example

Is it really free?

The app is absolutely free 👌

If you want to use the ORGanizer for Salesforce native integration you need a Full PRO or Team license, though, but for companies it can be a life saver!

How do you use ORGanizer Connector integration?

It’s easy as 1,2,3:

Install the package on your org (👉 AppExchange Link)
Open the Options page (right click on ORGanizer icon and select Options)
Select the Import/Export tab
In the ORGanizer Connector (PRO) section select a connection (i.e. a login already stored on ORGanizer that lets you login to the org where ORGanizer Connector is installed…I suggest using an OAuth login)
- Provided org can be a production org, a sandbox org or a Developer Edition org, no limitations!
Select a Backup record and click the Get Backup button
- Remember: you need to get the Backup’s Secret using the Send Secret by Email button on the Backup record
Select the logins you want to be loaded into ORGanizer for Salesforce extension
Select a login group already on your extension or create a new one and click the Import Logins button
- If you import a login that is already on ORGanizer (username is the unique key) the login will simply be updated with the new passoword and token

Have a look at the video below to have a glimpse of how simple is ORGanizer for Salesforce’s Connector user experience:

When will ORGanizer Connector be available to install from AppExchange?

UPDATE: The package has just been listed and is available from this 🔗 AppExchange link.

We hope to be ready to publish the listing within Christmas 2022 alogn with an updated version of ORGanizer for Salesforce extension that will enable the native integration for PRO users.

What if I need more details?

Contact me:

📣DevOps Center is now Generally Available!

By Enrico Murru

On December 16, 2022

In Post

Finally this amazing tool is GA!

DevOps Center is IMHO one of the most anticipated tools that we, the community of Salesforce professionals, were waiting since ages 👴

This gap has been filled in the years by many amazing products like Copado, Flosum, Gearset, AutoRABIT, Blue Canvas, Prodly or Opsera to name a few, but finally a Salesforce branded tool has just born to overcome many of the difficulties with Change Sets.

DevOps Center is a valid alternative to organize your work, track changes automatically, integrate seamlessly with GitHub (other GIT providers coming soon), and deploy updates easily with clicks: developers who are used to work on Git can still go on with it as DevOps center automatically updates its UI based on Git activity and admins can still participate in tracking changes on Git using clicks and not command line.

DevOps Center is available in any production org with Professional, Enterprise, or Unlimited Edition, or a Developer Edition org…so you can get your hands dirty!

Take a look at Salesforce Developers official blog for more links on how to learn!

💬Virtual chit-chat about being an MVP and the future of Salesforce [ITA]

By Enrico Murru

On December 13, 2022

In Post

Few days ago I’ve been interviewed by Carlo De Bonis for his Spaghetti Salesforce vlog (in Italian 🍕🍝).

We talked about my career path, what being a Salesforce MVP means and what I believe our amazing Trailblazer Community and Salesforce ecosystem will evolve in the next years.

Have a nice view!

Salesfore Spring ’23 coming!

By Enrico Murru

On December 12, 2022

In Post

This is the time of the year when a new release is about to arise from the epic forges of the Salesforce laboratories, where magic spells and powerful artifacts are built!

Here are the key dates to be considered:

December 12nd: you can get your own pre-release org to test the new features (use this link)
December 21st: release notes will be available on the help site(use this link)
January 6th: preview sandboxes gets the new release (for more info about how to handle sandboxes previews have a loog at this site)
The same days new Trailhead content will be published to handle your certification maintenance
January 10th: overview content is released to have a sneak peek of what’s new (e.g. have a look at the release in the box site, but the Get Ready for Release chapter on the release note should have all the links)
January 13rd, February 3rd, February 7th: Spring ’23 comes to all orgs, check the maintenance calendar to see which instances comes first!

📣Vlocity University Dismission imminent🚪

By Enrico Murru

On December 9, 2022

In Post

📣Salesforce Partners Announcement ⚠

Vlocity University courses has been migrated to Partner Learning Camp, the one-stop-shop for all Salesforce enablement.

All Vlocity University courses have been moved to PLC to deliver even greater value for customers and trusted partners.

Vlocity University is retiring on December 31, 2022.

What does this mean for Salesforce partners?

Wether you have or not a Vlocity University account, no worries at all: join the Partner Learning Camp.

You simply login to the Salesforce Partner Community, click the Learn tab, and then click the Start Learning button under Partner Learning Camp.