Are you (semi-)familiar with fflib but sometimes still feeling challenged to write constructive test methods, without copy-pasting everything? This post is more like an extensive guide, showing example code for reference, but also deep-diving into the why and how of certain lines of code.
StaticResources are publicly accessible
Did you think StaticResource were a save place to store data, as long as you not expose the name? This article shares how each StaticResource is publicly accessible for each Site and/or Community visitor.
OutboundMessage Acknowledgement to prevent duplicate retrievals
Are you still requiring Outbound Messages for your implementation? Be aware of the Acknowledgement being responded and keep track of NotificationId to prevent a message overload.
Restricted status codes for HTTP Response in Salesforce
Did you know Salesforce has limited the status codes which can be returned in a HTTP Response? This article lists the missing ones and elaborates on how to resolve this.
Static Resources in Communities Head Markup
Do you want to reference a Static Resource in your Community Head Markup? This article describes how to reference this, what use-cases might be useful and two challenges I faced when referencing a Static Resource within a Community.
RecordType restricted picklist values in Flow
Ever ran into the issue Picklist values were not restricted by RecordType in Lightning Flow Screens? That’s history! This simple Component can be easily added to your environment, allowing to only show valid picklist values.
CSS variables in Lightning Components
What are CSS Variables and how can they help you make your Lightning Web Components more maintainable and reusable? This article gives a short introduction on why and how to apply them, with a particular focus on Lightning Web Components.
Enterprise Design Pattern (fflib)
What is the Enterprise Design Pattern; why would you apply it; where and how to start? Implementing this pattern will help you structure your code base, promote reuse of methods and allow to reduce unit test runtime thanks to Mocking.