Johann Furmann’s Post

🚀 Exciting Discovery Alert! 📚 Dive into the World of Salesforce Architecture with "Salesforce Platform Enterprise Architecture" 🌐💡 Hey LinkedIn Tribe, Just had the incredible opportunity to get an exclusive sneak peek into the pages of "Salesforce Platform Enterprise Architecture" – and let me tell you, it's a game-changer for anyone in the Salesforce ecosystem! 🚀 🛠️ Unleash the Power of Salesforce: This book is your ultimate guide to mastering the intricacies of Salesforce architecture. It's not just a book; it's a roadmap to harnessing the full potential of the Salesforce platform. 🌐 Real-world Applications: The author seamlessly weaves real-world scenarios, case studies, and best practices into every chapter. You'll walk away with actionable insights that can elevate your Salesforce game immediately. 🔗 Trailblazing Strategies: From designing scalable solutions to optimizing performance, "Architecting Success" equips you with the strategies and techniques needed to architect success in your Salesforce journey. 💻 Stay Ahead of the Curve: In the rapidly evolving world of Salesforce, staying ahead is key. This book provides the latest insights into architecture trends, ensuring you're always on the cutting edge. Why should you get your hands on this gem? 📈 Elevate Your Salesforce Skills: Whether you're a seasoned Salesforce professional or just starting, this book is your secret weapon to take your skills to the next level. 🚀 Career Acceleration: Mastering Salesforce architecture opens doors to exciting career opportunities. Propel your career forward with the knowledge gained from this invaluable resource. Ready to embark on a transformative Salesforce journey? 🚀 Grab your copy of "Architecting Success" now! 📖✨ Available for purchase at amazon or your preferred bookstore. Let's architect success together! 💻🌐 #SalesforceArchitecture #Trailblazer #TechReads #ArchitectingSuccess #SalesforcePlatform 🚀

Flow Architecture & Naming Conventions | Feb 29th (LEAP DAY!) | Virtual Event | Portland Admin Group Starting your move from workflow rules (or Process Builder) to FLOWS? Already made the move and are thinking, "That's not quite perfect." How you think about and structure your FLOW architecture is key to long-term success. Special guest Dan Donin will share his methods for building, organizing, and naming his FLOW automations. NOTE: This meeting will not be recorded. This event is open so you can pop-in whenever you have the time (office hours style). We hope this invite finds you well and thriving in your Salesforce journey! As passionate advocates for continuous learning and collaboration, we are excited to invite you to an upcoming virtual event that promises to be an incredible opportunity for knowledge sharing and inspiration. We encourage you to showcase a problem you've solved or a creative item you've developed within your Salesforce implementation. Whether it's a complex automation workflow, a custom Lightning component, a customized report, or a brilliant solution to a business challenge, we want to hear about it! This is intended for end-users and is not a showcase for third-party apps. If you would like to present your bolt-on app/installed package, please reach out to the Community group team for consideration.

Whenever I need to do a discovery, (or Spike, or whatever you call them) and then design something new in Salesforce, I use a template to help me draft the initial solution and think through the problems. This isn't a technical architecture template, it is a solution architecture template (Although you should be thinking about both). How do you solve the business problem, can you define the why, what, and how, and whats the best approach to solve? This was built with a lot of collaboration between myself and co-workers like Joe, Tracy, Sean, and Ann (along with many, many, others) over several years of experience of doing discovery after discovery, spike after spike, and using this framework has helped me a lot to glide through solution building a bit more efficiently and also easily show others. This isn't the backlog tickets and can certainly skip over a lot of technical details, so don't forget those, but start with why, what, and how, and move on from there and I hope this helps and would love to hear what others are using. #salesforce #salesforcearchitect #salesforceadmin #discovery

Blueprint for architecture! 🌐 Learn step-by-step how to become a Salesforce Technical Architect. Unlock skills and insights for a thriving architectural career. 🏗️🚀 #Salesforce #SalesforceArchitect #CareerGuide

I've just posted my review of "Practical Salesforce Architecture" by Paul McCollum, UXMC - you can find the full video here on YouTube https://lnkd.in/eB6dJNZM Paul has written a great book 📖 full of useful advice that I would recommend to any enterprise architects trying to understand #Salesforce or #salesforcearchitect wanting to understand enterprise architecture a bit better. It's also a fantastic book for anyone working with Salesforce who wants to: 💬 communicate how Salesforce works to non-Salesforce people more effectively 📄 understand some documentation best practices and principles 🤝 understand what can be expected of different architect roles and how to succeed as an architect

https://lnkd.in/ecYEQ6VN For architects, consultants and admins who are looking to create diagrams to showcase there solutions, here is a refresher article on salesforce diagrams which you should leverage. It has templates for quick reuse and get the right diagram for your needs.

I often hear people talking about Salesforce Flow, discussing what it can achieve, but I rarely see anyone emphasizing design principles or design patterns in its use. This is the fundamental crux of the issue. Anyone can build a flow, but the crucial question is whether it will genuinely contribute to business value without considering a futuristic vision and the right design principles. Unfortunately, I believe it won't. Yes, anyone can create a flow, but there's a significant difference between constructing one with the right architecture and merely addressing the current problem at hand. If a flow is built without considering the broader architectural perspective, it may not qualify as a great architecture, and it might not bring sustained business value in the long term. As long as I don't see that conversation I am afraid I do not see that as an architecture conversation I rather take it as a tool conversation . If you are a salesforce architect I would love to see you take the following aspects into consideration Modularity, Scalability, Reuse and Composition, Error Handling, Governance and Security, Documentation, Testing, User Experience, Integration Considerations, and Performance Optimization.

Is your Salesforce Implementation not meeting expectations? watch a 1 min video: https://conta.cc/3x0rBKA Poor quality architecture can contribute to the failure of Salesforce projects. Architects play a critical role in the success of Salesforce implementations. They are responsible for designing the solution architecture and ensuring it aligns with business requirements, best practices, and scalability considerations. Here's how poor-quality architectecture can impact Salesforce projects: 1. Inadequate solution design 2. Over-customization 3. Lack of technical proficiency 4. Inadequate stakeholder engagement 5. Failure to address integration challenges Get a second opinion at https://lnkd.in/exURRqes

A great session from Moyez Thanawalla, Salesforce MVP! He mentioned being an adjunct professor at The University of Texas at Dallas, and the way he presented and interacted with the room and the humor incorporated into the presentation - you could tell that teaching was a natural thing for him! Great insights when it came to multi-cloud strategies! Some points he brought up: 1. Think about the strategy - not just the execution! 2. Avoid: >> One enterprise system to do it all >> Every department has its own >> The cheapest option or some random one your neighbor told you about 3. Understand the rules for the way your data is entered and updated 4. Make a choice for what system is your * Source of truth * 5. If any system is an "arbiter" and makes decisions in the process - have a plan for the possibility of going offline 6. There were talks about how Platform Events and Bus Architecture might be the next wave with the various benefits it has to offer!