In the previous article, you have learned how to use the Framework to set up Callout Resources with configurable and reusable parameters, and also to route every callout to an alternative endpoint which can be another resources server or Salesforce itself. You have got a glimp of what we call Mocking! We will deep dive into the concept of Mocking and its purposes and we will also speak about cool features around logging and tracking.
Callout means calling an external endpoint from Salesforce mostly through APEX when you have to integrate your org with any others systems. Basically, there is nothing very complex on implementing this, but what happens when you need to change something, when the external system resource is not ready or not yet developed, when you need to validate your feature without the availability of external resources and finally how can you test and track everything ? In this article, you will explore the new features of the framework helping you to achieve all of these.
OAuth Flow is a web authentication method that enables one user to authenticate in Salesforce in a secured way. In this post, I will demonstrate how to use Salesforce as identity provider for a Node.JS app hosted on Heroku.
JWT Bearer Flow is a server to server authentication method that enables one server to authenticate in Salesforce in a secured way.
It’s time to share my new framework with you :). I’ve been asked by all my colleagues (even if they are not part of the company anymore) where they can get my old framework, when they could have a new version or ongoing updates. I have simplify it, rework it from scratch to come with a releasable solution that can be shared with everyone.
This Framework is an accelerator that I’m working on since years and I’ve started to rethink the design based on project experience. The principal objectives is to bring guidelines to develop faster, to reduce code, to reuse components, to ensure high quality, to be compliant with governor limits, to be atomic, to be DRY compliant.
APEX code runs inside a transaction that was started by an interaction which represents a context of execution. Each context has its own behaviors and is sensible more or less to governor limits.
APEX is a development language similar to JAVA, that is used to build advanced automation in Salesforce Platform. As any of other language out in the world, some guidelines and code conventions has to be followed in order to build high quality applications.
This pattern will help you decide the way to implement Picklist. It can be designed in many ways and the implementation depends on the characteristics and the level of maintainability you are looking for.
This pattern will help you write Process Builder that can be activated or deactivated based on Profile or Permission Set assigned to user.
In the previous article, we have learned some basics to handle correctly SOQL within Apex Code, now we will focus on an important topic that is often unknown or not understand correctly. Here’s an overview of advanced queries to handle large data volumes.
Salesforce Secure Development Library 