Beyond Apex

In this series of articles we'll cover more advanced logging scenarios that extend beyond Apex code.

Oftentimes, we may have more than Apex code running in our environments. Salesforce offers a variety of technologies you might be using. Chances are, your org has a mix of Apex, LWC, and Flows, in varying proportions.

This makes troubleshooting considerably more complicated. What if a trigger kicks off a Flow and that Flow breaks? What if an LWC component kicks off some Apex code that breaks during a DML operation? What if there's a screen flow that invokes some Apex backend that kicks off a Flow? The number of such permutations one can encounter is vast. That's why we've put together some helpful tips to enable logging across any mix of technologies your team might be using.

The biggest problem with using a mix of platform technologies is being able to trace the execution throughout the entire transaction. Luckily, Triton has a way to deal with this and provide you with a unified trace of execution that includes ample details.

Read on for some of the more common examples. If you don't see your exact scenario covered, we'd love to hear from you!

We recommend you work through the examples below in the order they are presented.