Hi Daniel,

I've seen you that you asked for questions/remarks on debug logs at the end of the presentation.

I'm really used to read them and work with them with a dedicated app to parse them properly but I still have 1 big issue.

When working with apex, it's pretty easy to cycle through the order of execution and to understand which trigger start a new trigger on another object and so on.

But when it comes to flow, if there is a flow trigger, the element will close itself before handling the started trigger inside it. Making impossible to backtrack what the element started.

Not sure if you are the responsible for this but that would be nice if it could be modified in the future.

Other subject that is annoying regarding logs : 

The ApexExecutionOverlayAction is not working as expected ( at least for me) ^^

If I try to create one overlayAction for another user than me, it will never be triggered.

In order to work, I need to login as the user and create the overlay in apex so that it will be triggered properly. It's not a perfect solution and it relies on a dev that I need to push on the org if I want to be able to monitor in depth what's happening for my user.

Is it working as designed ?

Other subject regarding logs is related to apex execute anonymous. That would be great to be able to get the debug log associated without the need to have a traceflag

Thanks for you nice presentation on evalFormula, I completly miss the point that we can use object Apex Class . I was already convinced by the solution but I really see now how to explain it in depth during our next local dev group in Paris

Fabrice