The Pick street from list masking activity allows you to mask table places by replacing them with a value from the street picklists.
|Table of contents|
To use the Pick street from list masking activity, it must be placed inside a table masking activity or a similar activity that iterates over data. Once placed, you can choose the property you want to mask, and then select the type of data you want to replace it with. Furthermore, you can specify what subset of picklist data will be used to get the replacement values from.
Let's assume we want to mask street names in the Address table. We can do this by first placing the Address masking activity, and then placing the Pick street from list masking activity inside it. Then, we choose the Street column, and for the type of data to replace it with, we choose StreetName. We leave the picklist declaration as it is.
Figure 1: Street masking
|Property group||Property name||Description||Example|
|Input properties||DataItemProperty||The property to mask.||Write
|EnforceUnique||If true, random selection should select unique values.||
|Input: Filter||Filter||Expression used for filtering records - only filtered items will be masked.||
|SkipDefaultValues||If true, default values will be omitted in masking (i.e. null values are not masked).||
|Input: Lookup||LookupItems||Items to use for random selection of parameters during masking.||
|LookupProperty||Lookup item property whose value should be used as replacement value.||
|Input: Repeating||RepeaterId||The ID of the repeater that will be used to detect repeating and save results when masking item key repeats.||
|RepeatingKey||Key to use for repeating detection.||Write
|RepeatValueOnly||Whether repeaters should only save the used lookup value, and not entire lookup item.||
|Misc||DisplayName||Display name of the activity in the workflow.||
|Result||Contains the masking definition object. It's a part of the masking infrastructure and should be ignored.||-|
BizDataX Documentation © Built by Ekobit. All rights reserved.