Comments
1 comment
-
Official commentHi Kendra,
Hope you are doing well today, lets see what options we have available to us. After reading through your requirements for the custom e-mail mask, I am leaning towards having you try configuring a conditional dataset as described here: https://documentation.red-gate.com/testdatamanager/command-line-interface-cli/anonymization/masking/using-different-or-custom-datasets/conditional-datasets
Essentially a Conditional dataset lets you Apply masking only when a condition it true, otherwise, do something else, so for your logic it would be similar to: “If the email ends with @123.com, @456.com, or @789.com > keep the original value. Otherwise mask it"
As for making it global, once you have an anonymization treatment that does what you like, that treatment can then be ran against any database that has the same schema, each treatment is not locked to a single database. For tables with different names but the same e-mail column/schema, you would need to add each table to the tables array in your JSON document. I am including some documentation below that should help with this:
Give the above a read and let me know if you have any remaining questions or concerns and I can address them
Add comment
Please sign in to leave a comment.
I would like to create a custom email mask that only masks emails that do not end in the domains @123.com, @456.com and @789.com. I am finding information here and there, but nothing comprehensive that tells me exactly how to do it. I am not a json expert so understanding the structure is difficult and I have just started using the product so I'm struggling. Can someone detail exactly how I can accomplish this. I want to be able to apply it to all databases and tables so I don't want to just drop it in the code. I need a global option. Thank You,