Genesys Cloud - Main

Hello everyone,

How can I simplify the auditing process by using filters in Audit Viewer to track specific actions, such as deletions in data tables or changes in flows, without getting lost in the complex configuration of the available filters?

Hello, Alesson!

One usable feature is to make a test change replicating the specific scenario you're trying to audit.

Then, you can load the audit viewer inside the Genesys interface and look for the network logs to see how that request was made to the audit API endpoint.

That also is handy when you need to look for changes made outside the realtime audit API range.

Hello Daniel,

Thank you very much for the insight!

Hi Alesson, I also have that question, it's a great question and could greatly optimize the reading of audits on a daily basis.

------------------------------
Iury Santos
------------------------------

Hello, Alesson.

If you have almost the ID of the object, you can make a simple filter using the entity ID. Make things easier. 

Hi Alesson,

The Audit Viewer can definitely feel overwhelming, but the secret is to use a "Top-Down" filtering approach to cut through the noise. 

1. Start with the "Service Name"
To find exactly what you need, first select the relevant service. For changes related to flows or tables, you should generally select Architect.

2. Isolate the "Entity Type"
This is the most effective way to remove irrelevant data.

• For Flows: Set the Entity Type to Flow.
• For Data Tables: Set the Entity Type to DataTable.

Why? This immediately hides thousands of irrelevant system events like logins or permission checks.

3. Filter by "Action"
Once you have the right object, refine it by the specific action you are investigating:

• For Deletions: Select Delete, as shown in your configuration.
• For Changes: Look for Update or Publish to see version history.