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.
SOQL, Salesforce Object Query Language, is a proprietary language which aims to query Salesforce SObjects. There are many ways to write and test those queries, we will explore some with some use cases.
Before starting any implementation, one should establish a good homogeneous naming pattern for every component. It helps identify components quickly without struggling with some hazardous naming. All should be written in English and translation workbench should be used to give the correct output to the end user.
This pattern will help you write workflow rules that can be activated or deactivated based on Profile or Permission Set assigned to user.
