The Generate OIB masking activity allows you to generate OIBs.
|Table of contents|
To use the Generate OIB masking activity, it must be placed inside a table masking activity or a similar activity that iterates over data. Once placed, select the property you want to mask. Additionally, you can set the EnforceUnique property to make sure every generated credit card number is unique.
In this example we want to mask OIBs in the Customer table, so first we place the Account masking activity and put the Generate OIB masking activity within it. Once placed, we select the OIB property and leave other properties as they are.
Figure 1: Generating OIBs
|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: 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
|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.||-|