You create a mapping with a specific source and target and add the masking techniques as well. Over time, you add on more columns to the source table and want to mask those columns as well. The mapping then needs to be edited before it can be run again. To avoid having to edit the mapping, you can use a mask rule parameter when you configure it. You can then select columns to mask at runtime. If you added any columns after the mapping was created, you can select them at runtime without updating the mapping.

You might have source data in multiple databases. Rather than creating multiple mappings for each source and target combination, you might want to create a single mapping to mask your source data in any of the databases and load them to different target databases. To run a mapping with different source and target connections each time, you can use parameters for the source and target connections and objects. You then need to choose different masking techniques depending on the source connection. To do this, add a mask rule parameter to the data masking transformation in your mapping. You can then choose the source connection and object, the masking rules to apply to each column, and the target connection and object at runtime. You can run the same mapping multiple times after selecting different values for these fields depending on which source and target you want to use.