Tag Archives: salesforce admin

Salesforce Devops

Why is Salesforce so Late to the DevOps Game?

More IT teams are turning to DevOps as a solution to help them to solve incessant silos in their workflows. However, the question of why Salesforce has been so slow to adopt still remains on the minds of developers. The DevOps movement began to grow in 2007, spawned by development teams desperate for tools that solved their biggest pains. DevOps served to break down the brick wall between engineering teams and their operations counterparts so companies could keep up with demand for more frequent software releases. 

The Salesforce ecosystem’s slow adoption of DevOps can be attributed to the following key principles:

1. Salesforce is not a code first environment

Salesforce is a low-code platform that is declaratively configured as much as it’s programmatically configured. The declarative environment provided by Salesforce goes beyond the developer empowering a people with no coding experience to be citizen developers in control of their business processes. Often, Salesforce Administrators, Business Analysts and Project Managers have great ideas, but are excluded from conversations, due to their inability to work with code-heavy DevOps tools.

Successful adoption of DevOps for any team low-code, no-code citizen developers must be first class citizens from the very beginning. This is why AppOps is designed with the lowest technical user in mind. 

2. The production org has historically been the source of truth

In DevOps the code is the source of truth, not the software. The code is versioned and every change is stored in a repository, like track changes to a document, so it’s easy to roll back changes if there’s an error. Within Salesforce we think of production as the source of truth. The problem is production is always moving and changing, and there’s no real history of changes. 

For Salesforce DevOps to be successful we need to be able to version not just the code in Salesforce but the declarative configurations too. This is why AppOps helps you version your Salesforce data.

3. Creating reproducible environments has been challenging 

This principle is all about having a safe place to play around and test new ideas. You need to be able to create them quickly and toss them. Salesforce has sandboxes, but not truly reproductions of production because they don’t have all of your data. Even Full Copies get out of sync with production quickly and can only be refreshed every 30 days. Since Salesforce data is highly relational and those relationships are hard to maintain org to org, most companies fall into one of two buckets:

  • Everyone shares the Full or Partial Copy sandbox. All the work happens here and people stepping on each other’s toes, which results in restricting access to the 
  • They work in DevPro without data, meaning they can’t efficiently build new stuff or test it very well 

To be successful, you need to be able to create true copies of production and really fast. That’s why AppOps Sandbox seeding allows you to select, filter and seed data into any org in minutes. 

Schedule a demo to discover how AppOps can improve how your team manages data  Salesforce.

Demystifying Version Control: What Salesforce Admins Need to Know

Are you looking to upgrade your team’s efficiency while boosting the reliability and security in your new DevOps tool? AppOps is supported by end-to-end version control to support Salesforce admins in better managing testing and production changes.

Let’s dig into why you as a Salesforce administrator should be using a DevOps tool with a version control system (VCS).

What is version control?

Version control, sometimes called source control, simply means tracking and managing changes to software code to ensure developers are always working on the latest version. If you only have one developer writing code, it’s easy for her to keep track of the changes she’s making and how they impact previous code. But with multiple developers working on different parts of the code, it requires much more effort and communication to keep the changes straight. A VCS is a tool that makes tracking and managing change easier for teams. 

Teams maintaining Salesforce encounter the same challenges—lots of people working on different parts of Salesforce, lost work, and difficulty fixing mistakes. For admins trying to follow  an agile release management methodology, version control is essential.

How Can Admins Benefit from Version Control?

We commonly think of the production org as the source of truth, but with version control that changes. The VCS becomes the source of truth, putting an end to questions about the correct version, and providing several big benefits for admins.

Identify conflicts as they occur

When you’re working with multiple versions of your project, you can make those changes less the stress of affecting work being done by another member of your team. By enabling version control you remove the anxiety of creating conflict while implementing changes. 

Track revision history of changes over time 

Sometimes, while working with changes, you need to refer back to a specific change you scrapped previously. AppOps is equipped to support moving backward in time and being able to pluck and reconfigure your changes as simply as pointing and clicking. 

Work in a true agile environment

Agile release methodology is based on close collaboration and continuous improvement achieved via tight feedback cycles. For this to be effective both developers and admins need to work from the same source of truth and follow the same process for introducing change. The point here is to reconfigure workflows for teams to make them more easily consumable for admins and other team members. 

AppOps is designed to work in conjunction with your Salesforce deployment system for ease of implementation. Which means you don’t have to load up on multiple tools to get the benefits of version control. Prodly is designed for admins to simply point-and-click to complete versioning control tasks as well as version both your data and code. 

Set up a demo to learn more about implementing AppOps for your team.

Exploring Bidirectional Sandbox Seeding for Efficiency-Focused Teams

When you want to maximize your team’s efficiency and improve your end-user experience, AppOps can help you transform your entire workflow. By using this low-code option for DevOps, your team will be handling change requests like clockwork. And it all starts with efficiently seeding your Salesforce sandboxes.

When developers are only able to work with partial data, the chance of bugs and errors slowing down progress is immense. Many teams lose steam in the development and QA process when they go the route of manually working with a sandbox test data set. Bidirectional sandbox seeding bestows control to anyone who can click through a data management workflow. 

What is Bidirectional Sandbox Seeding?

Sandbox seeding is when you deploy data from your production org to a sandbox, whether it’s a freshly created org or you’re refreshing it. With AppOps, your team has the ability to move data in both directions, which makes it bidirectional. This makes for much better auditability of changes in production and deployment results. When your governance strategy is supported by AppOps, here’s what the process should look like:

Bidirectional Sandbox Seeding makes it so that once you start with a fresh sandbox and deploy data to it, you can move in any direction through this flowchart. Whether you’re rolling back changes to start from the beginning or just need to change a tiny detail, you’re able to move through these phases in just a few clicks. 

Why Should I Seed Sandboxes?

The first rule of maintaining Salesforce is “don’t make changes in production.” But far too often that means everyone working in the same full or partial org, making it difficult to keep track of who’s doing what, increasing the odds of stepping on each other’s work, and near impossible to find a good window of time to refresh the sandbox. Best practice states that instead, each individual should start each project in a dedicated sandbox and then promote changes to a shared QA org before releasing the change in production. This allows individuals to work faster and gives companies more thorough testing, better auditability of changes, and more effective usage of their expensive sandboxes.

So what’s stopping more Salesforce teams from adopting a better release workflow? The lack of representative production data in lower level sandboxes makes it harder to imagine, configure, and test changes. This problem becomes more complicated as changes move up the release pipeline and you need to keep all of the sandboxes in sync with production.  

What Does Sandbox Seeding Look Like Without AppOps?

Without AppOps, you’re literally out there on your own having to use a barrage of tools to handle what AppOps does seamlessly. There’s the tedious process of using a data loader, which can be compounded based on the size of your project. Some companies have to employ a 3rd party developer to manage their sandbox, which can become quite costly. With AppOps Release, you’re able to populate—and even anonymize— representative test data into five orgs in just a matter of minutes. Prodly gives you more control of your data, your processes, and a greater probability of aligning your people with the needs of your stakeholders for every project. 

How Can I Use AppOps to Improve my Salesforce Governance Strategy?

Having a seamless, automated process for seeding sandboxes increases org health, fights errors, and immensely improves efficiency. AppOps can help you move your data up, down, backwards and forward between your production org and sandboxes. This eliminates the need to depend on a full copy to work from as you advance through changes. You’re also able to configure data simulations, which means you can make changes without consequences.  When you need to deploy complex data from a schema all at once, no more worries about complications. Prodly gives you the power to migrate data from up to five orgs simultaneously.

See for yourself how easy and quick it is to seed sandboxes with AppOps Release. Watch the Bidirectional Sandbox Seeding Webinar (25 min).

What Salesforce Admins Need to Know about DevOps

As a Salesforce administrator, you’re one of the biggest change agents in any organization. But how do you control  your workflow and effectively affect change management? In recent years, Salesforce DevOps has been gaining traction as a way to better manage releases and drive faster innovation.  

While you may think DevOps is more of a category of interest for developers, think again, as there is much more to explore. When implemented correctly, DevOps empowers Salesforce administrators to affect organizational efficiency in a whole new way and enables anyone who has an idea to participate in implementing it. 

Can DevOps support me as a Salesforce administrator?

Allow your perspective to be transformed to fully understanding the benefits of DevOps. Also understand that implementing DevOps starts with a Salesforce Governance strategy surrounding how everyone on your team participates in the flow of change. By defining a strategy for making changes and implementing Salesforce DevOps tools to make it easier to follow the change process you can dramatically increase who gets to participate in the ideation process of change management. 

For many teams, the process of implementation is the daunting part of the process of adoption that causes a bit of anxiety. But rest assured that the pain of not having a tool supporting your change management processes is much greater and over time only leads to a more restrictive, risk averse attitude towards Salesforce release management where only a few people are trusted to participate in the process. DevOps aims to break down these silos and encourage more people to participate in the management of Salesforce. 

Can DevOps help you better support your team?

AppOps was designed with the understanding that Salesforce developers and administrators alike want to accelerate the pace of innovation without sacrificing trust. There’s also the opportunity for Salesforce teams to:

  • Foster greater collaboration
  • Create more opportunities for inclusion
  • Develop goals that focus on empowerment
  • Maximize overall growth
  • Clear backlogged projects faster
  • Change your risk stance from risk adverse to willing to experiment

DevOps is centered around helping you build and adopt a culture, mentality and processes that encourage innovation. Being in the driver’s seat means you are able to introduce ideas that help you to sustain your workflows more effectively. 

You’re also able to test those solutions without fear of your team taking a hit to its time and resources. Learning about DevOps as a viable solution for improving your team’s bottom line is a great step.

Can DevOps help Salesforce Administrators better manage risks?

DevOps has the power to transform your company’s perspective on innovation, risk aversion and inclusiveness. When every member of your team is engaged to ideate within a trusted process with the appropriate safeguards, you can achieve a more robust flow of solutions and opportunities for consistent growth and collaboration. Likewise, when everyone is engaged in spotting and managing risks, the chances of bottlenecks or silos in these situations are significantly reduced and the changes that are promoted to production are more thoroughly tested. 

DevOps addresses this by making it a priority from the strategy development phase. Which is where it should be handled, not when your team is drowning in a sea of requests. 

To learn more about how DevOps can support you as an admin, contact us