Skip to main content

#Release Management0 personne en discute

☀️ IN-PERSON SUMMER NETWORKING EVENT 

 📅 July 24 | 🕞 3:30–6:00 PM | 📍 Divine Barrel Brewing

 🍕 Food and drinks are included! 

 

🎲 Take the gamble out of your next Salesforce deployment!

Join the Charlotte Salesforce Admin Group for Release Survival: Taking the Gamble Out of Salesforce

  

Deployments & Summer Networking.

We’re excited to welcome Flosum (@Scott Cotter) for a featured presentation on practical ways to make Salesforce releases more predictable, reduce deployment risk, and avoid the last-minute surprises that can turn release day into a roll of the dice.

After the presentation, stick around for summer networking with fellow Salesforce professionals from across the Charlotte community. Whether you are an admin, developer, consultant, or simply looking to learn from others, we would love to see you there. 

 

☀️ Learn something new 

 🎤 Hear from the Flosum team 

 🤝 Connect with the community 

 🍕 Enjoy complimentary food and drinks 

 🎲 Leave release-day gambling behind 

 

Register here:

 https://trailblazercommunitygroups.com/events/details/salesforce-salesforce-admin-group-charlotte-united-states-presents-release-survival-taking-the-gamble-out-of-salesforce-deployments-amp-summer-networking/

 

Please RSVP only if you are confident you can attend, as in-person space is limited. 

 

#Devops  #Deployment  #Release Readiness  #Release Management

0/9000

 Introducing MetaDelta

: A Salesforce CLI Plugin Built for DevOps Teams 

 

As Salesforce DevOps engineers, we've all faced the same challenges:

 ❌ "Who modified this metadata?" 

 ❌ "What exactly was deployed?" 

 ❌ "Can I generate a package.xml only for what changed?" 

 ❌ "How do I audit Salesforce Core and Vlocity/DataPacks together?" 

 ❌ "How can I automate manual Salesforce Setup tasks?"

That's why I built MetaDelta, an open-source Salesforce CLI plugin focused on metadata auditing, deployment analysis, manifest generation, and manual task automation. 

🔍 Current Features

📊 Metadata Auditing

Identify metadata modified by a specific user within a configurable time window.

  •  Salesforce Core support 
  •  Vlocity / Industries support 
  •  User-based filtering 
  •  Change tracking across environments 
  •  Deployment investigation 

Perfect for answering:

📦 Smart Manifest Generation

Automatically generate deployment manifests from detected changes.

Supports:

  •  package.xml 
  •  package.yaml 
  •  Salesforce Core Metadata 
  •  Vlocity DataPacks 

Useful for:

  •  Hotfix deployments 
  •  UAT packaging 
  •  Release preparation 
  •  Partial deployments 

🔎 Deployment & Change Analysis

Analyze deployment activity and understand:

  •  What was deployed 
  •  When it was deployed 
  •  Which components were affected 
  •  Who performed the deployment 

A feature designed to reduce investigation time during incidents and release validation.

🤖 Manual Salesforce Setup Automation

One of the newest capabilities in MetaDelta.

Record and replay manual Salesforce Setup activities using Playwright-based automation.

Examples:

✅ Enable Salesforce features 

 ✅ Configure Agentforce settings 

 ✅ Navigate complex Setup pages 

 ✅ Standardize manual deployment steps 

 ✅ Reproduce setup tasks across multiple orgs

This helps transform traditionally undocumented manual activities into repeatable automation.

🎥 Record Once, Replay Everywhere

MetaDelta can:

  1.  Record manual Salesforce actions 
  2.  Generate executable automation scripts 
  3.  Replay them later across environments 

Great for:

  •  Sandbox setup 
  •  Release preparation 
  •  Environment standardization 
  •  Compliance processes

🎯 Built For

  •  Salesforce DevOps Engineers 
  •  Release Managers 
  •  Salesforce Architects 
  •  Vlocity / Salesforce Industries Teams 
  •  CI/CD Engineers 
  •  Enterprise Salesforce Programs

⭐ Why MetaDelta?

Most Salesforce tools focus on deployment.

MetaDelta focuses on:

✅ Understanding change 

 ✅ Auditing metadata 

 ✅ Generating deployment artifacts 

 ✅ Automating manual setup activities 

 ✅ Supporting both Salesforce Core and Vlocity ecosystems 

 

🔗 GitHub Repository

If you're interested in Salesforce DevOps, metadata governance, release management, or Salesforce Industries automation, I'd love your feedback.

MetaDelta GitHub Repository

⭐ Star the project if you find it useful.

Contributions, ideas, feature requests, and feedback are always welcome. 

 

 

Introducing MetaDelta: A Salesforce CLI Plugin Built for DevOps Teams As Salesforce DevOps engineers, we've all faced the same challenges: ❌

 

 

 

#Salesforce CLI  #Sfdx Plugins  #Salesforce Admin  #Devops  #Open Source Tool  #Release Management  #CICD

0/9000

The Release Updates Inventory and associated documentation has confusing details stated at the Release Updates Inventory which says: 

  • Should I continue to use the release updates section of the release notes? Yes. The Release Notes continue to be the source of truth for all Salesforce features including release updates. However, this inventory may provide an earlier notification of changes in advance of the release notes being updated.

I'm assuming 'this inventory' is referring to the Release Updates Inventory but it isn't clear. As stated by @Charlotte Innes, The Release Notes and the Release Updates are out of sync. In my case, 'Turn on Lightning Article Editor...' lists Enforcement scheduled for Spring '24 yet the Release Notes and the Release Updates Inventory state Winter '25.

 

Does Enforcement correlate to the Trust Status Maintenance tab date, in my case it is October 12 for the Winter '25 release. I'm assuming that means features enforced in Winter '25 will be enforced on October 12?

 

I realize this seems like a minor challenge for most organizations but in some cases, the enforcement dates enable features where there is no IT resources allocated to testing/early adoption. Thanks for the clarification.

2 réponses
0/9000

Our company (Finning CAT) is embracing Well Architected and moving towards better CI/CD, and especially Easy and Adaptable core principles.

One challenge we’re discussing is how to move away from org-based development to using source control and automated pipelines, while not losing the ability for admins (and citizen developers) to participate in the process to create low-code solutions quickly and efficiently. We’re currently using Azure DevOps for our core DevOps processes and agile ALM governance, and we’re looking closely at DX@scale as well as test automation since our org has grown a lot. We’re aware some organizations have seen success using Salesforce DevOps to allow admins to participate in the process without needing to get into the complexities of an IDE or CLI, so considering that too.

How have others tackled the challenge of moving to source control as the source of truth while preserving the low code promise of faster-time-to-deliver?

#Salesforce Developer #Devops #Salesforce Admin #Declarative #Maintainability #Release Management
0/9000
1 réponse
0/9000

When deploying change sets with new profiles, we're finding when the profile is created in the target environment, that extra object permissions are being added inadvertently. Why would this be happening and any idea how we can prevent it?

 

#Sales Cloud

New Profiles Deploying with Additional Object Permissions???

 

Screenshot - Target Environment.png

1 réponse
  1. 5 nov. 2021, 20:53

    Hi @Casey Rio,

     

    Profiles in change sets only include the permission related to objects in the change set. To ensure all permissions carry over, all objects need to be part of the change set. Which is to say all objects where the new profile should not have permissions available as part of the default profile. 

     

    It can be daunting depending on the release management process. I always used a newly refreshed sandbox as a bridge, pushing the updates from the development sandbox to the fresh sandbox. Then I replicate the change set from dev and add the object where permissions need to be managed. 

     

    HTH

    Regards,

    Scott S Nelson

    #Release Management

0/9000

Hi,

We are now testing MyTrailhead with a few licenses, but I was wondering if I could specify the permission sets. 

I have a Trailhead Editor permission set. I want the Editor to create and add content. I want them to add it to a release when ready and to preview it, but i just want to disable the Publish button under Releases.

When I disable the Release Management option in the permission set, then they cannot add content to a Release and cannot preview neither. They only have the Content tab and under actions they can only delete or edit their own content. Is there a workaround to add Release Management except for the Publish button?

8 commentaires
0/9000

Fala Pessoal, espero que estejam todos bem e em suas casas!

 

Estou passando aqui para relembrá-los que teremos na quinta uma sessão IMPERDÍVEL do @Tiago Nascimento  sobre Release Management com uma demo Hands-on show de bola.

 

Como teremos muito conteúdo, tivemos que adiantar a sessão em 30 minutos. Começaremos às 18:00 dessa vez.

 

**** IMPORTANTE ****

 

Atendendo a pedidos, aproveito também para deixar aqui a nossa playlist dos encontros virtuais anteriores no Youtube, para quem não conseguiu acompanhar todos eles. Salvem em seus bookmarks!.

 

https://www.youtube.com/playlist?list=PLWCkHg0zFNMfirjsUohpo47wj1-dDzIPj

 

Esperamos vocês!

 

@Leandro Esteves Barion  @T. Marinho 

 

@Arquitetos Salesforce de Clientes Brasil  @* Success - Português * 

 

#EncontroDeArquitetos  #Release Management  #Ci/cd 

5 commentaires
  1. 16 juin 2020, 21:29
    Olá @Fabricio Maia

    não encontrei o material apresentado no 7º encontro e o video também não está lá na playlist. Perdi esse evento e gostaria muito de poder assistir.

    Poderia disponibilizar esse material?

    Desde já agradeço e parabenizo pelas excelentes contribuições a comunidade.

0/9000

Hello Trailblazers!

 

We’ve heard from our customers that they would like to know more about how we keep our systems highly available and performant. Here’s a brief blog post that touches on 6 ways we do this.

  • Site Switch
  • Org Migration
  • Instance Refresh
  • Site Reliability Engineering
  • Problem Management
  • Change and Release Management

6 Ways We Deliver on Our Promise of Availability and Performance

1 commentaire
0/9000

Hi,

 

I imagine this has been asked before, just didn't seem to find it sorry.

 

Playground does not show 'Sandboxes' under setup.  So how do I try things in Trailhead teaching about release management without a playground to create a sandbox?

0/9000