26 Different Monitoring & Auditing Tools in Salesforce

Monitoring & Auditing Tools in Salesforce

There are quite a few Monitoring & Auditing tools in Salesforce to help you keep your Salesforce org healthy, secure, operational & efficient. With these tools, Admins and developers can monitor the configuration and usage and troubleshoot errors. Also they can report & block unusual user activity and/or set up notifications.

If you’ve ever watched a movie with a superhero, they usually manage to pull out the best gadgets at the right time.

As an Architect, Admin, Consultant or Developer you need to be aware of these tools and should know when and how to make good use of them. But let’s start with the first step – that is being aware of all the tools that you have in your arsenal.

The Auditing & Monitoring tools provided by Salesforce are both reactive and proactive. For example, if a user complains that the emails sent from Salesforce are not getting delivered to his or her clients then Debug Log and Email Log are the tools to use to troubleshoot. In this case you use these tools reactively i.e. after the event has already happened. Then there are tools that you can use proactively – like Transaction Security Policy that can be used to block  the users from downloading say more than 100 contact records from Salesforce and also notify an administrator.

In this blog, I have listed all these lifesaving tools which will come in handy when such unforeseen incidents happen, and you will know exactly where to look for to troubleshoot the problem. They are as follows: 

  1. Setup Audit Trail
  2. Login History
  3. Lightning Usage App
  4. Optimizer Report
  5. Health Check Report
  6. Portal Health Check Report
  7. Record Modification Fields
  8. Field History Tracking
  9. Field Audit Trail
  10. Transaction Security Policy
  11. Event Monitoring
  12. Apex Exception Email
  13. Debug Logs
  14. Email Logs
  15. Duplicate Error Logs
  16. Paused & Failed Flow Interviews
  17. Debug Flow
  18. Identity Provider Event Log
  19. API Usage Notification
  20. Article Imports
  21. Case Escalations
  22. Inbound Email Snapshots
  23. Entitlement Processes
  24. Outbound Messaging Delivery Status
  25. Time Based Workflow
  26. Source Security Scanner

Please do note that while most of these tools are free and is included in your Salesforce subscription, there are a couple that needs to be bought separately. I have mentioned that also in the presentation below. So, let’s learn about each of these a little more in details.

(We have discontinued our premium membership offering. If you are an existing premium member, you can still download the guides by clicking on “DOWNLOAD PDF [PREMIUM MEMBERS]” button. If you are not a premium member and want to download the guides, please sign up for our “All Access” pass. Complete details about this pass is available at this URL.)

Solution Options for Inbound Integration to Salesforce

What are the different solution options for Inbound Integration to Salesforce? That is sending data from external systems into Salesforce? Here is the list of options to choose from.

  1. Salesforce APIs
  2. Custom Apex Class
  3. Platform Events
  4. File Based Integration
  5. Other Salesforce/3rd Party Products

References & Useful URLs

3 Ways to Send Email from Salesforce Flow

#1MinuteTip There are three ways or options to send emails from Flow. Create Classic or Lightning Email template and create an Email Alert (this is what we have traditionally done for sending emails from Workflow Rules or Process Builder) and then you can use those email alerts in Flow to send email. The benefit of this approach is that you can leverage your existing templates and email alerts.

Or you can directly use the ‘Send Email’ option in Action Element of Flow. Optionally use resource type of ‘Text Template’ to define the email body and merge field syntax to dynamically populate field values at run time.

References & Useful URLs

Salesforce Release Lifecycle Stages – Pilot, Beta & GA

#1MinuteTip A Salesforce feature release goes through three different stages in its lifecycle. Here is what these stages look like:

  1. Pilot – Usually the first phase of public testing, Pilots normally include a small subset of participant Organizations. These Organization’s must request to opt in to a Pilot and then be nominated for participation.
  2. BETA – Features with successful Pilots will often transition to the BETA phase. This involves rolling the feature out publicly for testing. BETA features might require additional enabling by a System Admin and are accompanied by verbiage that clarifies the feature is in BETA status. BETA features are normally unsupported or given very limited Support as they are not yet fully functional or finished features.
  3. Generally Available (GA) – Once a feature has passed the Pilot and BETA testing phases it will be formally included in a Salesforce release. This is considered Generally Available (GA). GA features are considered fully functional and, in most cases, fully supported.
Salesforce Release Lifecycle Stages - Pilot, Beta & GA

References & Useful URLs

Salesforce Order of Execution Overview

#1MinuteTip In Salesforce, when you save a record, it goes through a series of steps before the record gets saved. For example, you may have defined triggers, workflow rules, flows, assignment rules, escalation rules etc. on your object. It will be important to know and understand the sequence in which these different components will get executed.

Here is a nice pictorial presentation from Salesforce Architects on the order in which different components are executed. You may want to take a print out and keep it front of you when designing the solution.

Salesforce Order of Execution Overview
Image Source:

References & Useful URLs

Scroll to Top