The cleanse assets that you create are available to the users who create mappings in
Data Integration
. You or other users add a Cleanse transformation to a mapping and add a cleanse asset to the transformation. The Cleanse transformation applies the logic in the cleanse asset to one or more input fields that you specify.
A Cleanse transformation works in a similar way to a Mapplet transformation. A
Data Integration
user connects the transformation inputs and outputs to other objects in the mapping in the same manner as a mapplet connects to other mapping objects. When the
Data Integration
user runs the mapping, the Cleanse transformation applies the cleanse asset logic to the input fields and generates an output field that you can connect to a downstream transformation.
After the mapping runs, you can evaluate the data output to determine if the data meets the standardization objectives.
Rules and guidelines for cleanse assets and mappings
Consider the following rules and guidelines when you work with mappings and cleanse assets:
A cleanse asset is a reusable object. A
Data Integration
user can add a cleanse asset to transformations in multiple mappings. A Cleanse transformation is a nonreusable object. You select a Cleanse transformation when you configure a mapping.
A cleanse asset is a read-only object in
Data Integration
. The cleanse asset does not change unless you update it in
Data Quality
.
To view the list of cleanse assets that you created in
Data Quality
, select the
Explore
option.
If you update a cleanse asset that you previously added to a transformation, you must synchronize the transformation with the cleanse asset.
To synchronize the transformation, open the transformation in the mapping and select the Cleanse properties.
Data Integration
displays a message that prompts you to synchronize the transformation with the cleanse asset.
ASK INFAPreview
