Today I came across another article over at Foxy Solutions which gives a great overview of how to implement Enterprise Design Patterns using FFLIB in Salesforce. It’s a 5 minute read where you can pick up some good tips, links to related material, and some good best practices to follow as well.
A few days ago I had some free time and decided to make something fun using Lightning Components and now finally you can play Minesweeper on Salesforce!
https://marchbanks05-developer-edition.eu14.force.com/ms/c/MS_App.app
Best played on a desktop browser as you’ll need to right click!
Have fun playing!
Sent off to get back Salesforce certification ranking from the Artisan Hub and here are my results! Ranked 6th within The Netherlands isn’t that bad if might say so!
https://about.artisans.com.au/salesforce-certified-professional-artisan-hub-launch
We’ve covered all of the layers so far in use when using FFLIB. Here’s a quick overview of the different layers again.
- Selector – all of your queries go into this layer.
- Domain – the layer which contains reusable pieces of code for working with sObjects and is the entry point for handling trigger events.
- Service – business logic orchestration layer which can be called from anywhere in your application.
- Unit of work – a pattern for managing transactions on the platform.
In this blog post I’m going to cover how to “stitch” all of those layers together to produce a rock solid code base and have an application structure which is properly set up.
In this blog post I’m writing about ApexMocks and one particular feature which I found extremely useful, argument capture. Argument capture can really enhance your unit testing capabilities within FFLIB and ApexMocks based projects.
A really useful plugin for hiding away all of the metadata XML files whilst you’re developing in Sublime 3 is ToggleExclude. Check out the package listing over on PackageControl.io to see how it can really help with helping you focus on the files which matter when developing.
https://packagecontrol.io/packages/ToggleExclude
Below is my configuration file for hiding away Apex class, Trigger, Visualforce Page, Visualforce Component and Lightning Component metadata files.
{
"conditional_file_exclude_patterns": [
"*.cls-meta.xml",
"*.component-meta.xml",
"*.page-meta.xml",
"*.trigger-meta.xml",
"*.cmp-meta.xml"
],
"enabled": true
}
Fantastic video from Salesforce explaining how to use the ApexMocks framework and the new Stub API. Highly worth watching if you’re interested in speeding up your unit tests or considering using the FFLIB framework.
One thing I hear from time to time is that Lightning Components can be a little slow, especially when rendering dynamic data. In this blog post I’m going to share some thoughts and approaches on how to speed up rendering times and improve the usability of your applications.
A fantastic new feature in Summer ’17 release of Salesforce now allows you to define which unit tests can safely be run in parallel!
If you’ve disabled running parallel unit testing in your Salesforce org because of issues with concurrency (i.e. UNABLE_TO_LOCK_ROW exception) then this update is for you! You can still keep running of unit tests in parallel disabled, but you can now optionally indicate which unit tests can be run in parallel.
To do this, modify the annotation on your unit tests to include the following new parameter.
@isTest(isParallel=true)
This should drastically speed up running of your unit tests in your Salesforce org! Find more on this in the Salesforce documentation:
Quirky Apex 