"The Trial. Clicks, Code, and Kafka"

Demo Code from the presentation held at CzechDreamin' '19 by Christian Szandor Knapp and Daniel Stange on August 16, 2019.

Session Abstract: "Code works just fine. Clicks work just fine. But when you combine code and clicks – Apex Trigger and Process Builder Actions for example, this is where you invite Kafka’s paradoxes – also known as WTFs? – into your Org: Everything looks peachy at the beginning, over time you add more functionality only to wake up one morning to find your org transformed into a gigantic bug.

In this session we will demonstrate how easy it is to really blow things up using code and clicks. And, of course, how to avoid this scenario altogether. We will put our – and your – assumptions on Trial: Is it true that Apex performs faster than Flow? Can CPU Time exceptions be avoided? Do best practices we know from Code apply to Clicks as well?"

Presentation Slides from Czech Dreamin' 19 on Google Drive

Assisted Deployments to a Scratch Org or a Developer Org

Use either of these two options to deploy straight into a Scratch Org or a Developer Org / Sandbox using the "Deploy To Salesforce DX" or "Deploy To Salesforce" buttons.

We strongly recommend not to deploy to Production Orgs. Our samples are build to benchmark

Build From Source with Salesforce DX

We have simplified the installation with Salesforce DX by providing a shell script. For Windows, run createScratchOrg.ps1 in Powershell For Mac/Unix/Linux, run createScratchOrg.sh in the terminal of choice.

The shell script performs the following steps:

• Create a scratch org from the included config file
• Installs MyTriggers as an Unlocked Package
• Pushes a release version of Logger to the scratch org
• Pushes the demo code & metadata to the scratch org
• Assigns the permission set LoggerPermissions to the running user
• Assigns the permission set CodeClicksKafka to the running user

If you want to manually build from scratch, please consider completing these steps before you try to run the examples.

Run the benchmarks

Run the record insert scripts

The folder benchmark contains a shell script to insert a number of records. To use the script, run

./insertNRecords.sh <number of records>

from your terminal (Mac/Linux/Unix) or

insertNRecords.ps1 <number of records>

from Powershell (Windows).

If you prefer to run the benchmark script from Developer Console or the command line, copy & paste the following:

List<Mock__c> lMocks = new List<Mock__c>();

for (Integer i = 0; i < $1; i++) {
		lMocks.add(new Mock__c(
			Name = 'Mock ' + String.valueOf(i)
		));
}

insert lMocks;

and set iNumberOfRecords to the desired number of records.

To execute code from the developer console, open Debug > Execute Anonymous from the menu.

To execute code from the SFDX CLI, run sfdx force:apex:execute Then paste the snippet and hit Ctrl + D to execute the code block and wait for the results.

Retrieve the resulting log files

To retrieve the operation's results, run sfdx force:apex:log:get from the Salesforce command line.

Filter what you want to see

Switching the logic

The sample code contains three Custom Metadata Type to configure the logic

• Logger
• MyTrigger Config
• Process Builder Config

Activate / Deactivate the Logger

Activate / Deactivate Triggers

Check the "Active" check box in the configuration to toggle Trigger code execution.

Control the Executed Units in Process Builder

Using this Custom Metadata Type record, you can select which unit will actually do the work that ProcessBuilder "Mock" is about to perform.

• "Node" - executes a node in the same Process Builder
• "Subprocess" - executes an invocable Process Builder ("createMockMocks")
• "Flow" - executes an autolaunched Flow ("createMockMocksFlow")
• "Apex" - executes an Invocable Method ("Invocable_MockMockService.createMockMock()")
• "Flow + 2x Apex" - executes an autolaunched Flow ("createDeepMockMocks") that sequentially invokes two Invocable Methods (Invocable_MockMockService.createMockMock(), Invocable_MockMockCheckService.checkMockMock())

Note: This only toggles the execution flow in the Process - You still have to activate / deactivate Process Builder manually.

Bulk Uploads

Utilize the Mocks.csv file to benchmark an insert of 200 Mock__c record into the org

Open Source Software

Our demo code makes use of Open Source software, published under the licenses stated below. Please review the license when using / adapting any code contained in this repository:

• Logger published by Christian Szandor Knapp. See https://github.com/Szandor72/logger
• MyTriggers published under MIT License by appero GmbH. See https://github.com/appero-com/MyTriggers