Anonymization in the LUCS database allows to hide personal Agent data from the reporting: Powerpivot, SSRS and Reporting Portal.

  • The data remains in the database and is available when using direct queries on tables.
  • A “base string” and number are used for compiling anonymous data. The base string is configurable and provides branding capabilities (e.g. you can use your company name for it).

Following table contains list of agent personal details (fields), used in reporting. In this example of anonymization, we re using base string “luware”

Field Name

Anonymization, using base string “luware”

AgentDisplayName

luware_1

AgentFirstName

luware_1

AgentLastName


AgentUserName

sip:luware_1@luware.com

Configure anonymization

Anonymization and application of the base string is done directly in database using SQL Server Management Studio.

This is a disruptive task. Please create database backups and don't perform this during operation hours!

The script values are stored in the following locations

  • [Reporting].[_SysSetup] table,
    (info) If [Reporting].[_SysSetup] setting is empty, original agent names will be left reports.
  • [SetupKey] = ‘ANONYM_AGENT_NAME’,
  • [SetupValue] = value of base string (is empty by default).
    (info) If a value is any other string (length>0), this string will be used as base string for anonymization. 

Enable anonymization script

Enable Agent Anonymization Script

UPDATE ss SET

[SetupValue] = ‘luware’ — replace it with base string value

FROM [Reporting].[_SysSetup] ss

WHERE [SetupKey] = ‘ANONYM_AGENT_NAME’
SQL


Disable anonymization script

Agent Anonymization Script

UPDATE ss SET

[SetupValue] = ”

FROM [Reporting].[_SysSetup] ss

WHERE [SetupKey] = ‘ANONYM_AGENT_NAME’
SQL

Execute data loader

In both enable or disable anonymization cases above you have to execute the stored procedure (Dataloader Script) for changes to take effect: 

Data Loader Script Execution