Procedure: Detailed

The GDPR utility will generate the output based on the values provided in the gdpr.properties file.This file is present under the GDPR folder.Configuration Details:

# Opportunity Detect Code of the Audience Level.
# The property reads as OpDetect.Audience.Name, and the value assigned is the 
# Audience Level code
# This is case sensitive.

OpDetect.Audience.Name=a
OpDetect.Audience.Name=1

# This property should be set to 1 if Campaign Integration tables 
# Expandedoutcome1 and Expandedoutcome2 query's are required
# Format used is OpDetect.<Audience>.isCampaignInt
#This property should not be blank

OpDetect.a.isCampaignInt=1
OpDetect.1.isCampaignInt=1

# History table is State table
# Name of this property should have the audience name. 
# Format used here is OpDetect.<Audience>.stateTable

OpDetect.a.stateTable=history
OpDetect.1.stateTable=history

# Outcome table contain the output
# Name of this property should have the audience name. 
# Format used here is OpDetect.<Audience>.outcomeTable

OpDetect.a.outcomeTable=outcome
OpDetect.1.outcomeTable=outcome

# OpDetect - Campaign Integration Table 1
# Name of this property should have the audience name. 
# Format used here is OpDetect.<Audience>.expandedoutcome1

OpDetect.a.expandedoutcome1=expandedoutcome1
OpDetect.1.expandedoutcome1=expandedoutcome1

# OpDetect - Campaign Integration Table 2
# Name of this property should have the audience name. 
# Format used here is OpDetect.<Audience>.expandedoutcome2

OpDetect.a.expandedoutcome2=expandedoutcome2
OpDetect.1.expandedoutcome2=expandedoutcome2

# Schema name used in campaign for campaign system tables.
# Name of this property should have the audience name. 
# Format used here is OpDetect.<Audience>.Db.Schema.Name
# This can be blank if no DB schema is used.

OpDetect.a.Db.Schema.Name=OD10
OpDetect.1.Db.Schema.Name=OD10

# Audience ID field for audience level 
# Name of this property should have the audience name. 
# Format used here is OpDetect.<Audience>.Field

OpDetect.a.Field=audienceId
OpDetect.1.Field=audienceId

# Data type for the Audience fields for the audience level 
# Name of this property should have the audience name and field name. 
# Format used here is OpDetect.<Audience>.<FieldName>.Datatype
# Valid values for this property is string.

OpDetect.a.audienceId.Datatype=string
OpDetect.1.audienceId.Datatype=string

# Absolute path to the input CSV file which has values for different columns defined 
# for audience level.
# Name of this property should have the audience name. 
# Format used here is OpDetect.<Audience>.Csv
# Note: must use forward slashes (/) or double-backslashes (\\)

OpDetect.a.Csv=C:/GDPR/sample1001.csv
OpDetect.1.Csv=C:/GDPR/sample1001.csv

# Absolute path to the output SQL file which will be generated by GDPR tool for audience level.
# Name of this property should have the audience name. 
# Format used here is OpDetect.<Audience>.Output
# Note: must use forward slashes (/) or double-backslashes (\\)

OpDetect.a.Output=C:/GDPR/sample1001.sql
OpDetect.1.Output=C:/GDPR/sample1002.sql

# Maximum size of the output file in megabytes. If value of this property is nonzero 
# then output files will be split if file size is going beyond the below given limit.
# Output file could be bit larger than the size specified by below property.
# Name of this property should have the audience name. 
# Format used here is OpDetect.<Audience>.Output.FileSizeLimit
# Only positive values are supported.

OpDetect.a.Output.FileSizeLimit=10
OpDetect.1.Output.FileSizeLimit=10

# Query separator character to be used for separating the queries.

QuerySeparator=;

# Nationalized string prefix to be used while generating the DB queries.
# If your audience name or value specified in csv file has non English characters 
# then N prefix should be used for MSSQL.

#Placeholder, not used in OpDetect.

# Do not modify

NLS.String.Prefix=

Update the csv file with the audience ID which needs to be removed as per GDPR compliance. Refer to the Configure GDPR properties step above for details regarding the csv file.

String values having special characters like space, comma, and so on in customer data should be enclosed in double quotes (“) in the input csv files.

Invoke gdpr_purge.sh script to execute the utility.

Errors can be checked in the gdpr.log file available at <OpDetection_Home>/tools/gdpr/logs.

The script created by the GDPR utility must be reviewed by a DBA before execution.

The script does not contain any commit statement. Users need to commit manually or set an autocommit as required.

The scripts must be executed on appropriate database schema after the review.

HCL Opportunity Detect down time is mandatory during the delete scripts execution.

The utility does not delete input records.