Winter’16 — Debugging: Customize Trace Flags

Winter’16 Release

Salesforce Winter’16 release has great features for administrators and developers for enabling debug logs and log levels for resolving application issues. The community has been waiting for this feature for a long time. Customizing trace flags and reuse in future is the best feature. Before this release, administrators and developers did not have flexibility of customizing trace flags and re-using the settings at a later point of time. Not anymore!
Further more, administrators and developers can set the times for the trace flag. This feature is available in Lightning UI as well as Aloha UI (Salesforce Classic).

Winter’16 — Setting new Trace flag

You can set the Debug Entity at the Salesforce User, Apex Trigger or a Apex Class. This is very handy, because one can set the debug flags at the user and individual classes, triggers all at one place.

Testing of the new feature

Rollup of Logs

When you specify start and end timings, no need to worry about logs expiring after 20 logs. The log are governed by the time limit instead of the 20 log limit before

Differences in Lightning UI

If you have enabled the new Lightning UI, the logs will show /aura instead of the OOTB object that is being worked on. For example, I was creating a task, the logs just showed /aura instead of /00T/e that old logs were shown. While the log contents were exactly same, I believe it is classic UI was more friendly

Difference in Logs in Aura and Salesforce Classic

Developer Console

I think, the developer console is much easier to set the debug logs levels now than setup. Developer/Administrator with basic knowledge can easily setup the debug preferences from this place instead of the setup.

Setting up of Debug Logs from Developer Console