Have you ever tried to address an issue with your code and gone down a rabbit hole? Of course you have. I recently encountered a pretty great one. It all started with this message from the console: Let’s set the stage. The endpoint for an existing integration (Remote Process Invocation – Request and Reply) was performing poorly so the client
I had reason this past week to work with Approval Processes in Apex. I guess I had never thought about it too deeply, but I was surprised to learn that these objects are all second-class objects. If you’re not familiar with the Approval Process architecture, there are five main objects: ProcessInstance represents an end-to-end approval process; ProcessInstanceWorkItem represents a user’s
One thing I somehow missed in the Spring ’16 update is a new method in the System.Test class called setCreatedDate() .
Something I’m consistently surprised to see is the misunderstanding around the two different types of keys in Salesforce. Every record has two keys: a 15-digit, case-insensitive key, and an 18-digit case-sensitive key.