Mapping Audits

Overview

Mapping audits are a way to track the values of individual mappings on a per job run basis.

---

Enabling Mapping Audits

There are two ways to enable mapping audits.

1. In the Mappings tab of your job. Click the eyeball next to any mapping. A green eye means the mapping is being "watched", and its values will be track

2. In the Details tab of your job, under the Auditing section, check Audit all Mappings. This will collect the audit data for every mapping on the job, including additional mappings from Job Mappings and Mapping Groups

---

Viewing audit data

Under the Audit Reports menu in the sidebar, click Mapping Audits. If there are no jobs with audited mappings, you should see a message saying so. Otherwise, you will be presented with a drop-down of jobs with mapping audits.

• Once you select the job, a drop-down with all job runs with audits will appear.

• Once you select your job run, a drop-down containing the audited mappings will appear.

• When you select an audited mapping, a table will appear showing you a count of the final values for that mapping.

These audits can be exported using the Export as CSV button.

---

Example: Content Type Breakdown

If you add a calculated field with the source '#{rd.mimetype}' (see the 3Sixty Expression Language) and audit it, you will be able to see a breakdown of all content types (pdf, docx) for documents in the job.

---

Example: Auditing a PII Job

If you add a PII Detection Task to a job, the field hasPii is automatically added to each document. You can add this as the source of a field mapping and audit it.

When viewing the mapping in the Mapping Audits page, you will get a breakdown of how many documents in the job contained PII.

---