Table of Contents

Search

  1. Preface
  2. Transformations
  3. Source transformation
  4. Target transformation
  5. Aggregator transformation
  6. Cleanse transformation
  7. Data Masking transformation
  8. Deduplicate transformation
  9. Expression transformation
  10. Filter transformation
  11. Hierarchy Builder transformation
  12. Hierarchy Parser transformation
  13. Hierarchy Processor transformation
  14. Input transformation
  15. Java transformation
  16. Java transformation API reference
  17. Joiner transformation
  18. Labeler transformation
  19. Lookup transformation
  20. Mapplet transformation
  21. Normalizer transformation
  22. Output transformation
  23. Parse transformation
  24. Python transformation
  25. Rank transformation
  26. Router transformation
  27. Rule Specification transformation
  28. Sequence Generator transformation
  29. Sorter transformation
  30. SQL transformation
  31. Structure Parser transformation
  32. Transaction Control transformation
  33. Union transformation
  34. Velocity transformation
  35. Verifier transformation
  36. Web Services transformation

Transformations

Transformations

Understanding input and output mappings

Understanding input and output mappings

The verifier asset that you add to the transformation is an address template with a preconfigured set of input and output fields. Each input and output field on the asset represents a different type of address information.
The data on the transformation input fields that you map to the verifier asset must reflect the types of information that the asset inputs expect. If the fields do not correspond, the mapping cannot evaluate the input data with full accuracy.
The asset inputs may expect a single element of address data, or they may expect multiple elements organized in a single field. Likewise, the asset outputs may write a single element of address data, or they may write multiple elements to a single field. If necessary, work with the asset designer to determine the meaning of the inputs.