10:30, Aplaus

Katka Vokrinkova

Kickstart Your Career With Mentorship Speed Friending, Katka Vokrinkova

Are you looking to grow or ready to guide? Join this fast-paced, 25-minute event where we bypass awkward networking for instant, meaningful connections.

Facilitated by an experienced mentor, this is a structured game that delivers a high-value network without the high-pressure commitment. We start with a fun, movement-based icebreaker to break down barriers, then dive into low-stakes 3-minute conversation rounds. We foster a safe space for all questions, emphasizing that peer-to-peer connections are often as powerful as finding a formal mentor.

The goal is simple: meet multiple Trailblazers, sense a potential match, and exchange contacts discreetly via a simple badge-scanning system. Attendees choose their follow-up (one 30-minute chat or longer mentorship) after the session, ensuring a no-pressure environment. Plus, every participant leaves with an exclusive list of experienced Trailblazers available for a 30-minute virtual chat.

11:00, Aplaus

Beech Horn

10 MuleSoft DevOps Practices Every CloudHub 2.0 Developer Needs to Know, Beech Horn

Discover ten essential MuleSoft DevOps practices for CloudHub 2.0 that improve observability, resilience, and Salesforce integration readiness.

This session covers implementing Kubernetes-style health endpoints, securing properties with HSM encryption, MDC logging, circuit breakers, API governance, and GitHub Actions CI/CD pipelines. You’ll also learn how to prepare your APIs for Salesforce API Catalog using OpenAPI and required tagging.

Key takeaways:

  • Implement /alive and /ready health monitoring
  • Secure secrets using protected runtime properties
  • Transition to OpenAPI for Salesforce API Catalog
  • Automate deployments with modern CI/CD practices

12:00, Aplaus

Fault Paths: I Avoided Them, Now I Report On Them, Aaron Crear

For the longest time I intentionally did not use Fault Paths in Flows. I saw this as unecessary as I was already getting the failure emails. I thought, why add something else? Until one day I had to show and justify to a client just how many failures their legacy automations were throwing. I came up with a simple, effective solution using Fault Paths, a Custom Object and Reports to track and show failures clearly.

12:30

Lunch time

Something typical counting with vegetarians and non-vegetarians as well. Beer (might be) included, as well as something sweet to get you ready for the next BIG thing.

13:40, Aplaus

Tomas Hnizdil

Discover before you build: Matching client expectations with Salesforce reality, Tomas Hnizdil

How many times has your Salesforce project reached a point where someone says, “I wish I knew this before”? While this often causes disappointment, Salesforce is rarely the problem, misaligned expectations not matching the platform reality usually are. This session focuses on embracing Salesforce’s strengths and constraints early during discovery and using them to set realistic expectations. Whether you are a consultant, architect, or sponsor planning a large Salesforce initiative, come to hear real-world lessons and mistakes from the field, so you can spot them early and avoid repeating them.

14:10, Aplaus

99% of Junior Developers Don’t Know what BAD Code is, Houssam Saoudy & Fátima Pérez Botón

This session will use bad implementations to demonstrate bad practices and offer solutions and practical advice.

14:40, Aplaus

Michał Bajdek

LWC Architecture for Enterprise Apps: Patterns That Scale Beyond a Single Component, Michał Bajdek

Building one LWC component is easy. Building an enterprise application with 50+ components that communicate, share state, and remain maintainable across multiple teams – that’s where things get interesting.

As a Salesforce Architect working on large-scale implementations, I’ve seen LWC projects start clean and gradually turn into an unmaintainable mess. The problem is rarely the framework itself – it’s the lack of architectural decisions made early on.

In this session, I’ll share the patterns and principles that separate a collection of components from a real enterprise frontend:

  • Communication patterns decision tree: When to use events, LMS, props, or a custom pub/sub – and why most teams pick wrong
  • State management strategies: How to handle shared state without turning every component into a spaghetti of @wire and imperative calls
  • Service layer in LWC: Abstracting Apex calls so your components don’t become tightly coupled to backend implementation
  • Component composition: Building truly reusable components vs the “reusable” components nobody actually reuses
  • Error handling architecture: A unified approach instead of try-catch chaos scattered across 50 components
  • Performance at scale: Lazy loading, caching strategies, and render cycle optimization for data-heavy UIs
  • Testing strategy: Unit testing LWC with Jest in a way that actually catches bugs, not just inflates coverage numbers

Each pattern comes with real code examples and a clear “when to use / when to avoid” guide.

I’ll also cover common mistakes I see in code reviews: oversized components that do everything, event chains that nobody can debug, and the classic “let’s put everything in a single LWC page” approach.

You’ll leave with an LWC architecture blueprint you can adapt for your own enterprise project.

15:10, Aplaus

Piotr Gajek

Beyond Best Practices: Why Following the Rules Can Break Your Code?, Piotr Gajek

In this session, we’ll challenge some of Salesforce’s “best practices” and explore why they aren’t always the best. We’ll also take a look at a few so-called “bad practices” that can actually work better than expected. This will be a deeply technical session, packed with code examples, real use cases, and honest discussion.

In this session, I want to show that we can break the rules – as long as we understand why. This session is for people who want to learn something new and explore ideas that might be a little controversial. As Metallica used to sing: open your mind for a different view.

15:40

Coffee break. Tea break. Sweet break. And something salt as well.

16:10, Aplaus

Aníbal García García

Bye-Bye Classic Approval Processes! Hello, New Salesforce Flow Approval Processes!, Aníbal García García

Approval processes have been around for a long time, enabling Salesforce professionals to create multi-step processes to control how records are approved. With the new Salesforce Flow Approval Processes, users now have a more flexible and powerful alternative that integrates seamlessly with other flows, enabling the automation of complex business processes.

Learn how to create a Flow Approval Process, send a record for approval, and approve it.