How to block a field from being mined

[Thrivikram]

Hi,

We are mining on Case table, mining results are showcasing 'Assigned to' which is a reference from sys_user table.

We want to to prevent mining on the “assigned to” field across the entire platform (thus not able to mine on assigned to across all table such as incident, case, hr etc).

To achieve this, suggestion was to add a new system property 'promin.limit.pii.tables' (Type : String) and add the reference table “User” as Value of the property. Its been explained it is a comma-separated property, so if we want to add another reference table we just add a comma and add that table as well.

We have added this property and its not working as expected. Mining results still show 'Assigned to'. How can we fix this?

[chirag_bagdai]

@Thrivikram - The property value is expecting extending table name such as "sys_user,sys_user_group". 

For example: if you want to block "assigned to" then you need to update the property to "sys_user" so, any field extending sys_user table will not be allowed.

[Thrivikram · Accepted solution]

@chirag_bagdai , Thank you. That worked. It throws an exception.

com.glide.process_optimization.exception.ClientException: Mining stopped: Project contains an activity definition or breakdown prohibited to include in a project. Remove personally identifiable information from your activity definition or breakdowns for entities :sn_customerservice_case[Activity Defs :Assigned to, BreakDowns: Assigned to]

chirag_bagdai