Masking activities

Masking activities are created after the features: importing data from the Portal and creating custom masking activities are used. Masking activities are contained as items in the Toolbox.

Table masking activities

After importing data from the Portal and rebuilding the package, a specific masking activity will be generated for every table in your imported data source. These masking activities will be grouped by their database schema in a Toolbox group with the following naming pattern:

PackageName.Datasources.DatasourceName.SchemaName

Each such group contains table-specific activities belonging to a schema. These activities have the following naming pattern:

TableName_Activity

Figure 1: Table masking activities of the schema dbo

These activities are combinations of other BizDataX masking activities such as a masking engine, masking iterators collection and masking items handler, and can be constructed from scratch if needed. The process of importing Portal data generates these activities to improve the process of creating an anonymization package, as you can quickly start defining masking algorithms of individual table columns.

Figure 2: Customer masking activity

Custom masking activities

After creating a custom masking activities and rebuilding the package, a specific masking activity will be generated for every custom masking activity in your BizDataX package. These masking activities will be grouped by their namespaces in a Toolbox group.

Figure 3: Custom masking activities

These activities can then immediately be used by placing them in your workflow where they will appear nested in an Activity masking activity.

Figure 4: Custom masking activity