devopsy.kinsta.cloud

Tag: Salesforce

  • Copado Streamlines Custom Salesforce App Testing

    Copado Streamlines Custom Salesforce App Testing

    Copado today added a testing tool to its platform for managing DevOps workflows in Salesforce application environments that automatically creates scripts based on manual tests being conducted.

    Announced at the TrailblazerDX conference hosted by Salesforce, Copado Explorer enables DevOps teams to integrate those scripts into testing processes that can be repeated as required.

    David Brooks, senior vice president and lead evangelist for Copado, said the goal is to make it simpler for DevOps teams to add those tests to the regression tests that are incorporated into pipelines created using the Copado continuous integration/continuous delivery (CI/CD) platform.

    In addition, markup and annotation tools enhance collaboration by allowing non-technical subject matter experts to provide detailed feedback and insights to quality assurance and development teams as part of an effort to streamline communications between product owners, testers and developers. Testers without a technical background can use that capability to contribute to the creation and deployment of effective automated tests. That capability makes it possible to shift testing further left to incorporate the business teams that better understand how an application should function, said Brooks.

    The challenge is far too many organizations still overlook the importance of testing, noted Brooks. There is a tendency when using low-code tools to assume that not as much testing is required because the tools that generate code create a false sense of instant quality despite flaws that might not manifest themselves until an application is deployed, noted Brooks.

    Rather than constantly updating applications, more testing should improve the quality of the applications being built sooner. That’s critical because most organizations don’t have the time and resources needed to continuously iterate applications until they eventually arrive at what the business requires, said Brooks.

    It’s still early days so far as the level of DevOps maturity that organizations using the Salesforce platform to build and deploy custom applications have thus far attained, noted Brooks. However, just about every organization that licenses the software-as-a-service (SaaS) platform from Salesforce customizes those applications to better align them with their internal business processes, he added.

    Each organization will naturally need to determine to what degree they are prepared to deploy customer applications, but it’s clear it’s becoming simpler to build them. Late last year, Copado, for example, added generative artificial intelligence (AI) tools to make it easier to manage the DevOps workflows used to build these applications, which means the speed at which these apps are built and deployed is about to exponentially increase.

    Salesforce, of course, is only one of many SaaS platforms that organizations rely on to build and deploy custom applications. However, as one of the most dominant platforms, the pace at which custom applications are being built continues to increase, with a larger percentage of these applications being built by professional developers familiar with DevOps best practices.

    Eventually, those DevOps workflows will be extended to every kind of developer, but for now, most organizations building applications are looking for more consistent outcomes regardless of what type of tool is used to build them.

  • Salesforce Adds Ability to Apply Custom Security Policies to APIs

    Salesforce Adds Ability to Apply Custom Security Policies to APIs

    Salesforce today added the ability to customize security policies for application programming interfaces (APIs) to the Mulesoft Anypoint API management platform.

    Gerry Egan, vice president of product management for Mulesoft at Salesforce, said this capability makes it possible for organizations to use an Anypoint Flex Gateway Policy Development Kit to streamline development of custom API security policies that can be implemented as code.

    In addition to providing integrations with integrated development environments (IDEs), the Anypoint Flex Gateway Policy Development Kit also provides test policies that can be employed to ensure API security.

    That approach makes it simpler to ensure APIs are secure as they are being built and deployed within the context of an automated DevOps workflow versus having to rely entirely on a separate API security platform, he noted.

    The Mulesoft Anypoint Gateway already comes with security policies that DevSecOps teams can readily implement. Salesforce is now adding the ability to apply custom policies that DevOps teams can apply as it becomes apparent cyberattacks against APIs are becoming more sophisticated, noted Egan. Those policies can, for example, be used to remove sensitive data or replace it with a token, he added.

    Responsibility for API security is often not well established in many organizations, but as more accountability for API security shifts left toward DevSecOps teams, there is growing interest in addressing the issue as code when APIs are developed and deployed. While cybersecurity teams are responsible for maintaining cybersecurity after APIs are deployed, few of them have any insight into how an API is crafted. That’s a significant issue because cybercriminals have become more adept at both exfiltrating data via external facing APIs in addition to manipulating the underlying business logic to compromise a digital process, noted Egan.

    The Mulesoft Anypoint Gateway automates the process of building and applying security policies to APIs as part of the software development life cycle (SDLC) in a way that minimizes any impact on developer productivity, he added. That approach provides the added benefit of reducing the level of cognitive load developers would otherwise experience if they had to manually create software policies, said Egan.

    In general, most APIs are internally facing, but it’s not uncommon for them to suddenly be exposed to the internet as application use cases evolve. The best way to ensure API security is at the point of creation. Providing developers with API security tools gives them an opportunity to address security issues at the beginning of the application development process.

    There have already been several cybersecurity breaches involving APIs in the past year. It may only be a matter of time before there are additional breaches that could prove catastrophic. Regardless of the size of the API breach, the application development team that created and deployed the API in the first place is ultimately going to be held accountable for fixing it. The challenge is to find the simplest way to eliminate the issue in the first place at a time when the number of APIs being built and deployed only continues to explode.

  • Copado Expands Beta of Generative AI Tools for Salesforce DevOps Platform

    Copado Expands Beta of Generative AI Tools for Salesforce DevOps Platform

    Copado today announced it has expanded a beta program through which it provides application development teams building applications for the Salesforce software-as-a-service (SaaS) platform access to generative artificial intelligence (AI) capabilities enabled by ChatGPT.

    David Brooks, SVP of Evangelism for Copado, said the company, via the usage of vector databases, has exposed instances of ChatGPT to everything in its knowledge base that has been collected over the last 10 years. That approach enables Copado to extend the large language model (LLM) used to train ChatGPT without exposing any data that might be used to one day train the next version of the generative AI platform.

    The goal is to enable DevOps teams to generate code and tests faster while simultaneously reducing the time required to handle support calls, said Brooks.

    In addition, Copado is using ChatGPT to enable impact analysis and conflict detection to reduce the level of friction encountered when deploying applications in a production environment. That latter capability is critical because, in many instances today, DevOps teams don’t have a firm understanding of how code needs to be deployed, resulting in unnecessary rollbacks of application deployments, noted Brooks.

    Generative AI will also automate the creation of documentation, such as release notes for every application deployed, to reduce the overall level of toil DevOps teams experience, noted Brooks.

    Copado also plans to provide governance tools that will enable DevOps teams to ensure the code written by an LLM is not based on a hallucination that results when trying to reconcile conflicting data, added Brooks. There will, of course, always be a need for a human to review code before it is deployed in a production environment, he added.

    In the longer term, Copado will make it possible for organizations to invoke multiple LLMs to address various functions as they best see fit, said Brooks. In fact, DevOps teams should expect to soon be employing multiple copilots trained to address specific tasks such as writing code, deploying applications, assessing cybersecurity and addressing compliance mandates, he added.
    Ultimately, application development and deployment efforts that today require weeks to complete will soon be accomplished within the same day, said Brooks.

    At the same time, organizations will also be able to better manage application environments that today operate at levels of scale few IT teams can manually track. Generative AI capabilities, in effect, will make it simpler for DevOps teams to effectively manage application environments at much higher levels of scale, said Brooks.

    Each organization will naturally need to determine to what degree they are prepared to absorb that level of innovation, but it’s clear the pace at which applications are built and deployed is about to exponentially increase. The issue organizations will increasingly encounter is that business processes will not be able to absorb the rate at which software can be built and updated.

    It’s not clear just yet to what extent generative AI will transform DevOps, but as advances continue to be made, many of the manual tasks and bottlenecks that today conspire to slow down application development and deployment are about to be eliminated in ways that few would have thought possible a little more than a year ago.

  • Salesforce Winter Release: What you Need to Know

    Salesforce Winter Release: What you Need to Know

    With the Salesforce Winter release dates behind us, it’s time to evaluate all of the new innovations added to your Salesforce ecosystem. Let’s just say that many users will be excited about the features added to this release cycle; plus, there were many anticipated updates that have finally come to fruition.

    Let’s dive right in and get to the meat of the release that will appease the administrator community, automate internal processes and close many operation gaps, and promote more team collaborations for you and your clients.

    Search Capabilities and Admin Processes

    These updates make an admin’s day-to-day work more streamlined, automated and convenient when it comes to getting things done.

    ● Configure Searchable Objects: This update allows admins to determine searchable objects available by Profile. This will allow users to broaden their search capabilities of records and more quickly and easily find what they need. For example, you can search for a picklist value and see all the records with that chosen value. Users, especially those in larger organizations, have been wanting this as it will streamline their process for customers. *This is in beta.
    ● Refine Your Search Results With Sort: Another win in the Search department – now you can sort your searches by different attributes and column headers. A nice “sigh of relief” feature for users, allowing them to find what they need faster. *Created because of users’ input on IdeaExchange.
    ● Dynamic Forms on Standard Objects: Administrators will very much appreciate this update as it streamlines the admin process with enhanced page performance and optional visibility rules. This will be rolled out everywhere except in three areas: Campaigns, products and tasks (though we really look forward to when this will be available here.) *Created because of users’ input on IdeaExchange.

    AI

    Since Einstein was introduced to the Salesforce community, it has helped users work smarter and faster, which is why seeing some of these key updates come to light, as noted below, has been a game-changer for many.

    ● Ability to Report on Emails Captured by Einstein Activity Capture (EAC): When EAC was first introduced, it was a huge weight off of admins because there was no more logging and it helped synchronize all conversations in one place. Over time, you couldn’t access or report on the data because it lived outside of SF, so you couldn’t compare it to other data in Salesforce, i.e., how many conversations does it take to close a deal? However, with this new update, you can! This is an enormous feature gap that has been filled, and will ultimately save people time and money as many would outsource this work to third-party vendors. *Created because of users’ input on IdeaExchange.● Call Summaries Powered by Einstein: This is fully available, and just a generally cool feature where Einstein will record voice and video calls and transform them into summaries that are editable and include next steps and customer feedback.
    ● Conversation Sentiment Analysis: This feature goes hand in hand with the call summaries because now, customer success agents can listen and view sentiments of a conversation between agent and customer, distinguishing if they are happy, calm, disgruntled, etc. There’s a sentiment score and visuals provided for easy reporting as well. This is a great feature for agent performance grading and identifying coaching opportunities.

     

    Flows

    Flows continues to be a priority and focus for Salesforce, and they certainly delivered on giving users what they want with these improvements.

    ● Screen Flows With Reactive Components: Users and developers will very much appreciate this update as it reduces the number of screens they have to click through. With reactive components, the user interface can react to the user and what it puts on the screen. Previously, in order to use the choice a user selected, you’d have to click “next” for it to recognize and load the next screen. This could turn into three to four “next” clicks to get where you need. Now, the choice can be calculated on the fly and the dependent choice will appear below, without the need for extra click-throughs!
    ● Custom Error Messages in Record-Trigger Flows: What was once an automated feature, now puts the user in the driver seat. With a custom error message, you can now create targeted – and user-friendly – error messages for your customers and explain what went wrong and/or how to correct it. This is a big win in our opinion, which will not only save the end user headaches and blockers but will also save your admin or consultant time researching where and what happened. This is now generally available – during the Summer release, this was still in beta. *Created because of users’ input on IdeaExchange.
    ● Autolaunched Flows Based on Data Changes in Data Cloud: Based on a data model object or calculated insight object, you can start a data cloud-triggered flow. This allows you to apply flows to your data cloud, storing all of your business data, and of course Salesforce data too.

    Callouts

    It wouldn’t be fair to close out the review of this release update before highlighting a few noteworthy callouts that will surely resonate with certain users, which include:

    ● Automated Site Check-Ins and Check-Outs: For mobile workers, this new feature protects their privacy while also tracking the times they arrive and leave job sites. It provides automated timestamps for location-based actions and gives you a report based on those insights. This is being piloted so not fully available yet.
    ● Controlled Tabs and Sub-Tabs: This change is currently in beta, but will resonate with the day-to-day user as it makes it immensely easier to manage these tabs with the methods they provide.

    There’s a lot to experience and discover within the Winter ‘24 release, from increased workflow to automated operations; any user will be happy. But Salesforce also delivered for its users. Many of the ideas posted on IdeaExchange are now reflected in these new features, which just goes to show that Salesforce is listening. Let’s continue using these innovations and work with Salesforce to continue bettering the overall experience for us and our customers. We can only imagine what Salesforce will conquer with the Spring ‘24 release!

  • DevOps Guide to the Salesforce Summer 2023 Release

    DevOps Guide to the Salesforce Summer 2023 Release

    The second installment of Salesforce’s 2023 releases provides some great eye candy for DevOps pros. From new admin features to user enhancements and the anticipated Flow updates, a lot is covered in the nearly 700-page Salesforce Summer ‘23 release. Let’s break down the highlights of some appealing features, why these updates will save all Salesforce users time and energy and explore key details of the impending transition to Flows.

    First, we’ll break down notable updates from this release that will save you time, help DevOps teams automate faster and enhance the experience for both you and your customers.

    User Enhancements

    There are lots of great adjustments to some tools we know you’ve been waiting for and some we hope will be made available to all users.

    ● Mass Quick Actions on Related Lists: This is a beta feature that you can opt-in to try. You can now add and update records directly from a related list—a time and tab saver! This feature has been requested many times and will decrease the need for custom-built interfaces. For instance, if you’re on an Account and want to edit the related Contacts, you can add, edit or mass update directly from the Account screen. This saves clicks and stops new tabs from opening and losing your spot, etc. Allowing users to update in bulk is a major win!

    ● Einstein Search: Advance your search capabilities by having additional field types to search within, such as picklist, which were not previously searchable. For example, if you have a picklist field on Contact, you can search for one of the values and any records with that selected value will appear. Users will get more relevant results in their search. This new enhancement is in beta, so we’d highly suggest opting in to give it a test drive.

    ● Lightning reports and dashboards improvements, including:

    Enhanced reports and dashboards with images and text descriptions let you add visualizations to your dashboards with company logos, helpful imagery or clarifying text. Explain exactly what the Dashboard is providing with helpful messaging or encourage the sales team with positive feedback about their work. This will not only better guide end users throughout the dashboard but will also increase engagement and personalization.

    Additional dashboard filters permitted: Dashboard filter allowance jumped from 3 to 5, making dashboards more configurable and customizable for different views and end users.

    A new ‘post to Slack’ option on dashboards: share analytics across your Slack workspaces so your colleagues can view, share, and subscribe to dashboard details and view in real-time.

    Note: While all of these improvements to reports and dashboards are amazing features, they are only available to unlimited edition users. We hope Salesforce will trickle this down to enterprise users soon.

    ● MFA auto-enablement continues: Unless you’re using a single sign-on (SSO) solution like Okta, Salesforce mandates the use of multifactor authentication (MFA). Hard enforcement is coming by spring 2024 when Salesforce initiates a full rollout, so we’d suggest getting ahead of it by implementing this now.

    Flows

    With the forthcoming transition to Flows, we find that the more Salesforce does with Flows, the better. In general, it gives users better tools to deliver to customers and offers better experiences overall. These Flow Builder updates are key:

    ● Send API callouts without using code (this is in beta). This is like having Postman-like capabilities right in Flow!

    ● Create screens that react to changes from other components on the same screen. This is huge, since you can’t create reactive screens in Flows right now. Workflow optimization is all about reducing clicks, which users can now achieve with reactive forms (this is also in beta).

    ● Log emails and use email templates with the ‘Send Email’ action. This was rigid before, as users had to pull in their own templates or make very basic emails in Flows. This is a basic but hugely helpful upgrade.

    Honorable Mentions

    • The new Undo field change feature: A lot of you have been waiting for this (ourselves included) since there is no such thing as “undo” in Salesforce … until now!
    • New Salesforce connect adapter for GraphQL: Developers and system architects will be happy to see this feature that allows you to access your external data by connecting to AWS Aurora via GraphQL queries from Salesforce as if the data were native. This saves you from having to copy and store your external data in Salesforce with complicated syncs.

    We’re all always hunting for ways to save time and simplify processes. Once again, Salesforce delivered with the Summer ‘23 release. Fewer clicks, bulk actions and more sharing and collaboration capabilities. And this one has a little bit of excitement for everyone–admins, developers and end users.

    The best thing you can do is to experiment with ways to optimize. There’s a lot in beta, so roll your sleeves up and dig in! Happy summer!

  • 4 Salesforce DevOps Adoption Challenges

    4 Salesforce DevOps Adoption Challenges

    In today’s ultra-competitive digital landscape, adopting DevOps practices has become crucial for organizations looking to accelerate their development processes and enhance software delivery. Salesforce is no exception to this trend.

    Salesforce DevOps essentially refers to applying DevOps principles and practices to the development and deployment of applications and customizations on the Salesforce platform. When done right, it integrates development and operations teams and offers numerous benefits, including better collaboration, faster release cycles and improved code quality.

    Furthermore, Salesforce DevOps empowers organizations to adapt rapidly to changing business requirements, respond to complex customer needs faster and improve their experience via process automation (for instance, streamlining the product configuration and price quote generation process with CPQ automation) and drive innovation more efficiently on the Salesforce platform.

    However, while the advantages of Salesforce DevOps are evident, its adoption comes with its fair share of challenges. In this article, we will dive into the four core hurdles that organizations face when embracing Salesforce DevOps. Moreover, we will provide actionable tips to tackle these challenges head-on, helping you ensure a successful Salesforce DevOps adoption journey.

    1. Siloed Development and Operations Teams

    DevOps isn’t just about technology and automation; it is also about people. In the realm of Salesforce DevOps, one of the most significant challenges that organizations encounter is the existence of siloed development and operations teams. Traditionally, these two teams have operated independently, often with minimal interaction, leading to fragmented workflows and hindered collaboration.

    This disconnect between dev and ops can impede the delivery of high-quality Salesforce applications and features. The lack of timely communication and coordination can result in misaligned priorities, delays in deployment, and an increased risk of errors during the release process.

    Moreover, siloed teams can stifle innovation and limit the potential for continuous improvement. The development team may create features that do not align with the operational requirements or may not be feasible to deploy efficiently. On the other hand, the operations team might struggle to understand the intricacies of the development process, hindering their ability to provide valuable insights or feedback.

    To overcome the challenge of siloed development and operations teams in Salesforce DevOps, organizations must foster a culture of collaboration and shared responsibility. Here’s how:

    • Promote cross-functional collaboration: Encourage regular meetings and knowledge-sharing sessions between development and operations teams. Foster an environment where team members feel comfortable discussing challenges, sharing insights, and jointly working towards solutions.
    • Break down communication barriers: Utilize collaboration tools such as Slack and Asana that facilitate seamless communication and information sharing between teams. This can help reduce misunderstandings and keep everyone informed.
    • Align incentives and goals: Create shared objectives and metrics that encourage both development and operations teams to work together towards common goals such as improving product-market fit or feature adoption. Recognize and reward collaborative efforts to reinforce the importance of cross-functional teamwork.

    2. Version Control and Source Code Management

    Effective version control and source code management are vital pillars of successful Salesforce DevOps practices. However, many organizations with layered dev teams find it tricky, leading to complexities, inefficiencies, and potential risks in their development processes.

    Version control is essential for tracking changes to Salesforce customizations and configurations over time. Without proper versioning, development teams may find it difficult to collaborate, understand changes made by others, or revert to previous states in case of issues. Additionally, source code management allows for better organization and control of codebases, ensuring consistent and reliable deployments.

    To tackle the challenges related to version control and source code management in Salesforce DevOps, teams should implement best practices and use appropriate tools. Here’s how:

    • Adopt a version control system: Implement a robust version control system, such as Git, specifically tailored for Salesforce projects. Git allows teams to track changes, manage branches, and collaborate efficiently.
    • Establish clear branching strategies: Define clear and consistent branching strategies for different development scenarios, such as feature development, bug fixes, and releases. This helps manage parallel development efforts and ensures smooth collaboration.
    • Encourage code reviews and collaboration: Conduct regular code reviews to ensure code quality, identify potential issues, and ensure compliance with best practices. Encouraging collaboration during code reviews fosters knowledge sharing and enhances the overall development process.
    • Automate deployments and rollbacks: Integrate version control with your Continuous Integration and Continuous Deployment (CI/CD) pipeline to automate deployments. This reduces the risk of manual errors and facilitates easy rollbacks in case of issues.
    • Educate and train development teams: Provide training on version control best practices and tools to ensure all team members are familiar with the processes and benefits of using version control effectively.

    3. Continuous Integration and Deployment

    Continuous Integration and Deployment (CI/CD) are core principles in the DevOps methodology that aim to automate and streamline the software delivery process. However, implementing effective CI/CD practices for Salesforce development can be a daunting task for large-scale enterprise companies, presenting them with various challenges along the way.

    One of the primary challenges in CI/CD for Salesforce is the complexity of customizations and configurations. Salesforce projects often involve multiple components, such as Apex classes, triggers, Visualforce pages, and metadata configurations. Coordinating the integration and deployment of these components in a seamless and automated manner can be intricate, leading to potential bottlenecks and delays.

    Moreover, organizations may encounter difficulties in ensuring the stability and reliability of their CI/CD pipelines. Incomplete or inaccurate tests, improper versioning, and inadequate rollback mechanisms can result in the introduction of bugs or errors into the production environment.

    Here are a few ways to combat this challenge:

    • Automate the build and deployment process: Use Salesforce-specific CI/CD tools that automate the build and deployment process, reducing manual intervention and ensuring consistency in deployments.
    • Implement comprehensive testing: Incorporate automated testing into the CI/CD pipeline to validate changes and ensure code quality. This includes unit tests, integration tests and regression tests to detect issues early in the development life cycle.
    • Use sandboxes for testing and staging: Utilize Salesforce sandboxes to test changes in environments that mimic the production setup. This allows teams to identify and address issues before deploying to the production org.
    • Establish version control for metadata: Use version control for Salesforce metadata to keep track of changes and enable seamless collaboration among developers working on different features.
    • Monitor and optimize pipeline performance: Continuously monitor the CI/CD pipeline to identify areas of improvement and optimize the deployment process for speed and efficiency.

    4. Test Automation and Code Quality

    Test automation and code quality are critical aspects of Salesforce DevOps that directly impact the reliability and performance of applications. However, organizations often have a tough time when it comes to implementing comprehensive test automation and ensuring consistently high code quality in their Salesforce projects.

    Manual testing can be time-consuming, error-prone and insufficient to keep up with the speed of Agile and DevOps development practices. The lack of automated testing can lead to delays in identifying bugs, lower confidence in code changes and a higher risk of regression issues when deploying new features.

    Furthermore, maintaining code quality becomes challenging as Salesforce projects grow in size and complexity. Without adequate quality control measures, development teams may introduce code that does not adhere to best practices, leading to suboptimal performance, security vulnerabilities and increased technical debt.

    Here are a few tips to tackle this challenge:

    • Implement automated testing frameworks: Utilize Salesforce’s built-in testing capabilities, such as Apex unit tests and Lightning Web Component (LWC) tests, to automate the validation of code changes and functionalities.
    • Adopt test automation tools: Consider leveraging third-party test automation tools that can extend and enhance your testing capabilities, such as Selenium for end-to-end testing of Salesforce applications.
    • Create a comprehensive test suite: Develop a comprehensive suite of test cases that cover different aspects of your Salesforce application, including positive and negative scenarios, boundary testing, and integration testing.
    • Integrate testing into CI/CD pipelines: Incorporate automated testing into your CI/CD pipeline to ensure that code changes are automatically tested before being deployed to production.
    • Conduct regular code reviews: As mentioned earlier, establish a culture of code reviews to assess code quality, identify potential issues and ensure adherence to coding standards and best practices.
    • Invest in code analysis tools: Use code analysis tools such as SonarQube and CodeScan to identify potential bugs, security vulnerabilities and maintainability issues in your Salesforce codebase.

    Wrapping up

    Embracing Salesforce DevOps offers numerous benefits for organizations, including increased collaboration, faster delivery cycles, and improved software quality.

    From breaking down silos between development and operations teams to establishing robust version control and source code management practices, addressing CI/CD complexities, implementing test automation, and prioritizing code quality, a lot goes into driving successful Salesforce DevOps adoption. Armed with the solutions, it’s time to implement them, adapt them to your organization’s unique needs, and embark on a journey of unmatched quality and collaboration in your Salesforce projects.

  • Salesforce Spring 2023 Release: Out With the Old, A Lot of the New

    Salesforce Spring 2023 Release: Out With the Old, A Lot of the New

    Salesforce is the connector and enabler of so many critical business functions. But that doesn’t mean it doesn’t come with its headaches. The environment is so complex that it really takes a conscious, focused effort to properly leverage all that Salesforce has to offer, as well as stay up-to-speed on everything that’s new and evolving.

    The Salesforce spring ‘23 release brought a lot of change. Some old tools disappeared and new products, dashboards and automation tools were introduced that admins will have to adapt to. There’s a lot to catch up on.

    Combing through the 600+ pages of release notes, there are three main themes represented in the spring release that will be useful to the entire organization, from DevOps and RevOps to sales and marketing teams, including: 1) new admin and developer tools and dashboards, 2) doubling down on low-code/no-code with enhancement to Flow and 3) commitment to security and permissions best practices.

    Admin and Developer Updates

    From an administrator’s and developer’s perspective, there are some exciting new features that will undoubtedly improve DevOps’ day-to-day. For instance:

    • Flows – allows you to migrate your old automations.
      • Connect to external data source (beta)
      • Support for lookup fields
      • Reactive screens (reduce the number of “Next” clicks)
      • Removal of “Iteration Limit Exceeded” governor limits
      • Element descriptions are now visible on the canvas
      • Migrate to Flow from Process Builder

    • DevOps Center – Still in V1, but it provides developers with a new interface.
      • Getting on the software development life cycle bandwagon so we can all say goodbye to change sets – finally!
    • Dashboards – Now you can insert text and graphics around charts.
      • Collections – organize reports and dashboard into logical collections that are free from their folder hierarchy. While they will still “live” in their folders, they can be accessed from a collection as well.
      • Add image and text components in your Dashboard to make better experiences with additional information, descriptions, instructions or whatever you want.

    These updates are not only useful for DevOps but, from an executive viewpoint, are extremely useful to showcase the business’s data with a clearer perspective. In other words, the new dashboards have more options to provide additional context and insight. In general, the user interface is not only more organized but can be navigated at a significantly faster rate than before.

    Doubling Down on Flow

    As the old adage goes, “Out with the old, in with the new;” Salesforce will be retiring the automation tools Workflows and Process Builders and converting them to Flow. The reason Salesforce is making this move—and ultimately forcing users to Flow—is because Workflows and Process Builders don’t have the flexibility or functionality that Flow does. Flow can create automation and provide great screen experiences that derive a far greater bandwidth of context and situational logic. The additions made to this much-anticipated migration tool will help administrators convert their current automation into Flow with less stress and hassle than rebuilding them all from scratch.

    So what is the timeline for this migration? Salesforce plans on blocking the ability to create new Process Builders in the Summer ‘23 release but has admitted that it’s not a hard date and will look at the success of customers’ migrations to Flow and feedback from the community. They have not yet announced a date for complete retirement but expect it to come sometime in 2025. That said, users should start doing this now. With any major change to your Salesforce environment, a plan is always recommended, especially with such a huge migration like this one. Given the amount of data and processes most organizations already have in place, we suggest taking time to strategize and test your migration prior to releasing it directly to Flow to make sure your order of operations for your automation is clear and follows best practices. Analyze your business processes and confirm with your users that these processes are still accurate.

    Commitment to Security

    As organizations lean more on Salesforce as their primary business operating system, Salesforce is becoming a critical piece of infrastructure rather than just software that businesses consume. It is also the “build-and-develop” nature of Salesforce that has more companies treating Salesforce as software they build rather than just software they use. The ripple effect is that as companies build within Salesforce, more developers are responsible for deploying and managing data. With that comes the responsibility for security and compliance.

    This has traditionally been handled as an administrative task, but now, Salesforce has created the tools for true enterprise infrastructure security and data management with permission sets and permission set groups. Even though permission sets have been around a while, the introduction of permission set groups and the growing need to transition permissions into more complex structures have changed the way permission sets are being consumed. Permission sets were previously used for basic exceptions to the permissions provided by profiles, but now they are front and center, providing even more organizational capability with Permission Set Groups (and their muting capability, but that’s a different story).

    Salesforce has taken note and announced the partial end of permissions within profiles as they lean into the new, better way to manage permissions. Profiles won’t be gone entirely, as they will still be needed for basic defaults, i.e., defining users’ default app selections. However, while Permission Sets will still have the responsibility for what apps you have access to, it will be the Profile that states which one is your default. This is also true for other types of assignments where there needs to be a single source of truth, like page layout assignments.

    Salesforce said they will be enforcing this plan in 2026 but are beginning to make sure everyone gets on board now by releasing great new tools to make this transition smoother, including user access policies and access to Permission Sets when adding new fields (currently only available for profiles). For large organizations, three years is just around the corner when it means implementing major overhauls in technology and philosophy to the business. While some are heading to building Permission Sets based on each object, I’d recommend basing them on features or functional areas to have the most control and the clearest overview of your new vast area of Permission Sets.

    Next Salesforce Release

    Overall, the spring ‘23 release was jam-packed with content to boost productivity, strengthen security, enhance the user experience and improve the overall business functionality. There are two Salesforce releases still to come in 2023, and I’ll be dissecting them both to highlight the most critical changes that can help you better your business. I’m looking forward to seeing what the summer ‘23 release has in store – any predictions on what Salesforce will come up with next? I’ve got a few guesses…

  • DevOps Adoption in Salesforce Environments is Advancing

    DevOps Adoption in Salesforce Environments is Advancing

    A global survey of DevOps professionals building apps in Salesforce environments found 44% of respondents reported their organization has a continuous integration/continuous delivery (CI/CD) platform in place, with another 39% planning to adopt one.

    The survey, conducted by Gearset, a provider of a DevOps platform for building custom applications in Salesforce environments, polled 1,254 DevOps professionals that are building and deploying custom applications on top of the Salesforce software-as-a-service (SaaS) platform. The survey also found nearly half (49%) implemented change monitoring, with another 33% planning to follow suit. More than half (52%) implemented source-drive workflows, with another 33% similarly planning to follow suit. A total of 41% of respondents noted that, over the last 12 months, they have more custom code to manage.

    Overall, the survey found 54% of respondents reported increased productivity, followed by improved quality and faster releases at 41% each. Nearly three-quarters (72%) reported they are able to deploy changes from one environment to another within four hours. Well over a third (39%) of this group are able to complete a deployment in less than an hour. Just under a quarter (23%) are also able to release code multiple times a week.

    However, only 18% can release a new feature to production in less than a day. Nearly half can complete the release within one day to a week. A total of 43% claimed that less than 10% of releases include a bug or error, with 46% reporting they can roll back a release in a day or less, if needed. Just over a third can restore a process in a day or less.

    The biggest obstacle to DevOps adoption is lack of experience (41%), followed by a third (29%) of respondents that reported difficulties with collaboration and another 29% that experienced limited buy-in from the rest of the application development team. Only 30% received DevOps training once a month, with 50% citing additional CI/CD and automation training as their biggest need.

    Despite these issues, a full 98% are generating a return on their DevOps investments, with 59% of teams reporting returns of over $10,000 per month and 40% reporting returns in excess of $50,000 per month. The top two priorities for the next 12 months are to consolidate systems and processes and improve flexibility, tied at 47% each, followed closely by 43% that noted that digital business transformation is a top priority.

    David Runciman, technical content manager for Gearset, said that while Salesforce applications are based on unique object architecture, it’s apparent that organizations are extending those applications using, for example, low-code tools more quickly. The issue that creates is, as organizations move to deploy these applications, they are encountering bottlenecks that conspire to slow the pace of innovation, he noted.

    The maturity level of DevOps teams building these applications will naturally vary. However, as the number of applications being built—especially by professional developers—increases, it’s only a matter of time before more organizations embrace DevOps best practices to bring order to the chaos, noted Runciman. While there may be some citizen developers building applications in Salesforce environments, the bulk of enterprise-class applications are built by professional developers that typically appreciate DevOps best practices, he added.

    The issue remaining is just how quickly those DevOps teams will be able to implement DevOps best practices as demand for additional applications grows.

  • Salesforce Launches Low-Code DevOps Platform

    Salesforce Launches Low-Code DevOps Platform

    Salesforce made generally available today a low-code DevOps Center service on its infrastructure through which developers are provided an opinionated platform for building custom applications. The Salesforce DevOps Center service is based on the same object model Salesforce uses to construct its own applications.

    Karen Fidelak, senior director of product management at Salesforce, said after nearly two years of development effort, this platform will make it simpler for both professional and citizen developers to build applications consistently using a common Source Control repository. That’s especially critical for professional developers that may need to access source code previously created by a citizen developer, Fidelak noted.

    In 2023, Salesforce will embed more robust continuous integration/continuous delivery (CI/CD) capabilities within the platform to make it simpler to deploy custom applications on the Salesforce platform, Fidelak added.

    In general, the number of developers willing to embrace DevOps best practices to build Salesforce applications has been surprising, since the platform was initially launched in 2020, noted Fidelak. She noted that both citizen and professional developers are looking to adopt best practices that provide a set of guardrails that ensure high-quality applications are secure. Salesforce anticipated a much higher level of DevOps resistance, added Fidelak.

    The DevOps Center platform enables development teams to track and deploy changes to custom objects on the Salesforce platform as Work Items that can be integrated with other Salesforce Flows, a set of process management tools the company provides. As development teams make changes in their sandboxes, DevOps Center automatically tracks them. Developers can then point and click to promote their desired metadata components via custom pipelines they define.

    In addition, Salesforce also provides optional integrations with version control systems such as GitHub to centralize the management and governance of artifacts.

    Finally, Salesforce is committing to tightening integration between DevOps Center and multiple software-as-as-service applications such as Tableau and middleware platforms such as Mulesoft, said Fidelak.

    It’s not clear how much low-code is moving through DevOps pipelines these days, but the volume is increasing as more developers rely on these tools to accelerate application development. The issue that creates is citizen developers typically don’t have the expertise required to build and deploy secure applications at scale—at least not applications that anybody other than themselves really wants to use. Ideally, citizen developers should be supported by application development platforms and DevOps teams that ensure security guardrails are in place for building applications at scale. DevOps teams should also reduce the friction that a citizen developer will most certainly encounter when building any application.

    The fact is, in the absence of that support, most citizen developers—who typically have other tasks that require their attention—will simply abandon an application development project should projects become overly complicated. None of this means organizations shouldn’t be working toward building their own army of citizen developers. The increased reliance on citizen developers is part of an inexorable wave of the democratization of IT. The challenge is making sure those applications are of the highest quality possible regardless of who actually developed them.

  • Recession! DevOps Hiring Freeze | Data Centers Suck (Power) | Intel to ‘be’ Wi-Fi 7

    Recession! DevOps Hiring Freeze | Data Centers Suck (Power) | Intel to ‘be’ Wi-Fi 7

    Welcome to The Long View—where we peruse the news of the week and strip it to the essentials. Let’s work out what really matters.

    This week: Engineer jobs are being cut, cloud infrastructure is using too much energy, and Intel’s 802.11be silicon is alive. (more…)