Skip to main content

Audit Application Release V0.1. by JET BI

About Us
Published by jetbi
30 August 2023
38

Currently, it is not possible to get all the important information about the Salesforce organization with one click. It requires opening many pages and executing a large number of commands, which takes a lot of time. At JET BI we find a solution - the Audit tool - a product designed to simplify the audit process of Salesforce organizations.

The Audit app is used to monitor Salesforce organizations and obtain information about the amount of metadata, organization settings, memory used, etc. During the audit, the user launches an application that is fed a script with a set of commands that must be executed in the browser. As a result, the application displays the result in a JSON file, which then converts the data and saves it to a doc file.

To start the audit process, you need to create an audit template (by the name of the audit type) and its items (commands that should be performed in the browser during the audit). Each audit template item record contains information about a single action in the browser, it can be a mouse click, text input, or getting text from any block of the page.

audit-tool-1

 

Records from the same template must be numbered in order using the Order Number field so that all actions in the browser are performed in the correct sequence.

During the use of the audit template, the browser executes automatic commands to retrieve data from the pages. For example, he can open the Developer Console and execute SOQL queries.

For the automatic audit process of the SF organization, authorization credits are submitted to the application, which must be pre-encrypted and placed in a special configuration file. This ensures reliable data security.

The audit result is returned in a new JSON file, which is then submitted to the Salesforce organization and, in case of successful parsing, Audit Items records are created. After that, the user can get the result in the form of a doc file and save it.

audit-tool-2

 

The generated doc file should look in the following format

audit-tool-3

 

Thus, the user can determine for himself which data from the SF organization he wants to receive. To do this, you need to know which URL in the browser it needs to go to and which commands to execute. These commands can be saved in script, and then used in any browser automatically, without the need for manual actions. The same script can be used repeatedly for similar SF organizations for a quick audit.

So, the tool Audit helps to solve a number of potential problems that may arise when determining all the characteristics of an organization, as well as reduce the time to obtain all the necessary information for users, and as you know, time is money.

If you are interested in Audit please fill out the form and our managers will contact you within 1 business day.


Evgeniy Klukach
Project Manager / Certified Salesforce Consultant, Administrator
image
image

We have available resources to start working on your project within 5 business days

1 UX Designer

image

1 Admin

image

2 QA engineers

image

1 Consultant

image
Related Articles
All articles
image
Is Salesforce Winning the Public Sector Race?
An analysis of Salesforce's rapid expansion into the U.S. public sector, tracing its path from cautious early government licensing deals in the 2010s through the launch of Government Cloud in 2012, its pivotal role in COVID-19 vaccine rollouts, and its 2025–2026 push into military and intelligence work via Agentforce and Missionforce. The piece covers major 2026 contracts — including a $5.6 billion Army deal, a $1.6 billion VA agreement, and Pentagon Impact Level 5 authorization — alongside real-world case studies like California's REAL ID processing and the UK's NHS back-office operations. It also examines the structural obstacles still facing Salesforce and other vendors in government tech: legacy IT systems decades old, outdated federal procurement rules, budget constraints, and organizational caution around AI adoption, plus the competitive pressure from Palantir, Microsoft, and Oracle in the race for public sector AI spending.
28 August 2026
image
Why Your Salesforce Flows Are Agentforce's Biggest Problem
This article argues that the most underestimated risk in Agentforce deployments isn't data quality — it's the automation layer: years of overlapping Flows, Process Builder processes, Apex triggers, and managed package logic that no one has reviewed end-to-end. It explains why AI agents inherit automation complexity without the tribal knowledge human admins carry, why technical debt only becomes visible after an agent hits it in production, and why a clean demo is no indicator of production readiness. The article closes with a concrete, tool-by-tool inventory approach using Flow Trigger Explorer, Salesforce Optimizer, Setup Audit Trail, Apex Debug Logs, Agent Builder, and Health Check — scoped to the specific processes the agent will actually use rather than the whole org.
23 July 2026
image
How to Wire Multiple Salesforce Projects in One Org Without Breaking Everything
This article maps the real integration patterns that emerge when multiple Salesforce projects — both managed packages and unpackaged code — share a single org. It covers four concrete patterns: attaching custom triggers to package-owned objects, calling global members exposed by managed packages, writing directly into another project's objects, and runtime-guarded reads of package data. It then addresses access control for authenticated and guest users, including the Master-Detail wall and the without sharing elevation pattern. The piece closes with eight concrete risks (compile-time dependencies that block uninstall, upgrade coupling, silent cascade failures, access invisible to admins) and six actionable recommendations for keeping cross-project coupling manageable.
08 July 2026