In the Column List:
- P = Primary key
- M = Mandatory field
- F = Foreign key (where the term is used loosely to indicate a surrogate key reference to a field in another table, not a formal constraint)
- DV = Default value
This table provides details about General Data Protection Regulation (GDPR) "export" or "forget" requests that were processed successfully. A row is added to this table for each field that might have contained an instance of personally identifiable information (PII) specified in the customer-provided JSON file.
The following tables and columns potentially contain PII:
|For Consumer GDPR Requests|
|INTERACTION_FACT|| SOURCE_ADDRESS |
|Custom user data fact tables (e.g., IRF_USER_DATA_CUST_1)||CUSTOM_DATA_*|
|For Employee GDPR Requests|
For audit purposes, a value of "NULL" in a record indicates that the field was evaluated for a particular instance of PII and was found to be empty.
By default, data is retained in the CTL_GDPR_HISTORY table for 15 days. You can configure the days-to-keep-gdpr-history option to specify a different retention period, up to 30 days.
For more information about Genesys Info Mart support for GDPR compliance, see General Data Protection Regulation (GDPR) and Genesys Info Mart Support for GDPR in the Genesys Security Deployment Guide.
The instance of PII that was searched for. The value is derived from one of the following consumer- or employee-identifying attributes in the customer-provided JSON input file:
- For consumers:
- For employees:
The ID of the table record in which the PII was found. A value of NULL indicates that a particular table was evaluated for that PII and no instance was found.
The name of the table that was evaluated for PII. (See the table description above for possible values.)
The name of the column that was evaluated for PII. (See the table description above for possible values.)
The name of the custom user data KVP key or custom Outbound Contact Server (OCS) record field that the customer has identified might contain PII and, therefore, has specified in the "gim-attached-data" element in the JSON input file. For example, while consumers are identified in Genesys Info Mart only by phone number or email address, custom KVPs or record fields might contain PII such as a name, Social Security number, or mailing address. The custom key would already have been mapped to a custom user data table and column or a RECORD_FIELD_* column in the CONTACT_ATTEMPT_FACT table, when you configured your Genesys Info Mart deployment.
In Cloud deployments, this column might also specify a non-custom KEY_NAME, such as “TRANSCRIPTION.”
The value of the custom user data KVP or custom OCS record field that contained the PII.
The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key is used for data lineage purposes.
The surrogate key that is used to join the TENANT dimension to other tables in the Info Mart database.
Indicates whether the PII was processed for a "forget" request: 0 = No, 1 = Yes
The UTC-equivalent value of the date and time of row creation.
|Improves search performance.|
|Improves purge performance.|
No subject area information available.