Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Table of Contents

Search

  1. Preface
  2. Working with Transformations
  3. Address Validator Transformation
  4. Aggregator Transformation
  5. Association Transformation
  6. Bad Record Exception Transformation
  7. Case Converter Transformation
  8. Classifier Transformation
  9. Cleanse transformation
  10. Comparison Transformation
  11. Custom Transformation
  12. Custom Transformation Functions
  13. Consolidation Transformation
  14. Data Masking Transformation
  15. Data Masking Examples
  16. Decision Transformation
  17. Duplicate Record Exception Transformation
  18. Dynamic Lookup Cache
  19. Expression Transformation
  20. External Procedure Transformation
  21. Filter Transformation
  22. HTTP Transformation
  23. Identity Resolution Transformation
  24. Java Transformation
  25. Java Transformation API Reference
  26. Java Expressions
  27. Java Transformation Example
  28. Joiner Transformation
  29. Key Generator Transformation
  30. Labeler Transformation
  31. Lookup Transformation
  32. Lookup Caches
  33. Match Transformation
  34. Match Transformations in Field Analysis
  35. Match Transformations in Identity Analysis
  36. Merge Transformation
  37. Normalizer Transformation
  38. Parser Transformation
  39. Rank Transformation
  40. Router Transformation
  41. Sequence Generator Transformation
  42. Sorter Transformation
  43. Source Qualifier Transformation
  44. SQL Transformation
  45. Using the SQL Transformation in a Mapping
  46. Stored Procedure Transformation
  47. Standardizer Transformation
  48. Transaction Control Transformation
  49. Union Transformation
  50. Unstructured Data Transformation
  51. Update Strategy Transformation
  52. Weighted Average Transformation
  53. XML Transformations

Transformation Guide

Transformation Guide

Cleanse transformation configuration

Cleanse transformation configuration

When you configure a Cleanse transformation in a mapping, you first select the cleanse asset that contains the logic to include in the transformation. Next, you map one or more incoming fields on the transformation to target fields that cleanse asset specifies.
The steps to configure the transformation depend on the number of inputs that the cleanse asset specifies.
To configure the transformation, complete the following tasks:
  1. Connect the Cleanse transformation to a Source transformation or other upstream object.
  2. On the
    Cleanse
    tab, select the cleanse asset that you want to include in the transformation.
    You can select a cleanse asset that contains a single input or multiple inputs.
    • If you include a cleanse asset that contains a single input, you can select one or more fields from upstream objects as inputs. To map the fields to the cleanse asset, click
      Add
      .
      The following image shows the options that you use to select the cleanse asset and add the input fields:
      The image shows the Cleanse tab of the transformation. The tab properties include a Select button that adds a cleanse asset to the transformation and an Add button that adds input fields that you can map to the asset.
    • If you include a cleanse asset that contains multiple inputs, the Add option does not appear on the Cleanse tab. Use the Field Mapping tab options to connect the transformation input fields to the asset.
  3. On the
    Incoming Fields
    tab, verify the incoming fields.
    By default, the transformation inherits all incoming fields from any connected upstream object in the mapping. You can define a field rule to limit or rename the incoming fields.
  4. On the
    Field Mapping
    tab, connect one or more input fields on the transformation to the asset. If the cleanse asset specifies a single input, Data Integration automatically links the incoming fields with the target field. If the cleanse asset specifies multiple inputs, link the incoming fields to the fields manually.
    The cleanse asset input names might reflect the names of the transformation input fields. If so, you can use the
    Automap
    options to connect the fields.
    The following image shows the options that you can use to map the input fields in the transformation:
    The image shows the Field Mapping tab of the Cleanse transformation. Use the field mapping options to identify one or more incoming fields that the transformation will read and the target fields that will carry the outcome of the cleansing operation.
  5. Verify the output field properties on the
    Output Fields
    tab.
  6. You can optionally rename the Cleanse transformation and add a description on the
    General
    tab. You can also update the tracing level for the transformation on the
    Advanced
    tab. The default tracing level is Normal.

0 COMMENTS

We’d like to hear from you!