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. Data Services transformation
  9. Deduplicate transformation
  10. Expression transformation
  11. Filter transformation
  12. Hierarchy Builder transformation
  13. Hierarchy Parser transformation
  14. Hierarchy Processor transformation
  15. Input transformation
  16. Java transformation
  17. Java transformation API reference
  18. Joiner transformation
  19. Labeler transformation
  20. Lookup transformation
  21. Machine Learning transformation
  22. Mapplet transformation
  23. Normalizer transformation
  24. Output transformation
  25. Parse transformation
  26. Python transformation
  27. Rank transformation
  28. Router transformation
  29. Rule Specification transformation
  30. Sequence Generator transformation
  31. Sorter transformation
  32. SQL transformation
  33. Structure Parser transformation
  34. Transaction Control transformation
  35. Union transformation
  36. Velocity transformation
  37. Verifier transformation
  38. Web Services transformation

Transformations

Transformations

Rule Specification transformation configuration

Rule Specification transformation configuration

When you configure a Rule Specification transformation in a mapping, you first select the rule specification asset that contains the logic to include in the mapping. Next, you configure the incoming fields and the field mappings. Then, you verify the output fields.
To configure the transformation, complete the following tasks:
  1. Connect the Rule Specification transformation to a Source transformation or other upstream object.
  2. On the
    Rule Specification
    tab, select the rule specification that you want to include in the transformation.
    The following image shows the options that you use to select the rule specification:
    The image shows the Rule Specification tab of the transformation. The tab properties include a Select button that you can use to add a rule specification asset to the transformation.
  3. On the
    Incoming Fields
    tab, configure 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, configure the field mapping options to connect the data from the incoming fields to the target fields on the rule specification asset.
    The rule specification inputs might already reflect the names of the input fields in the data. If so, you can use the
    Automap
    options to connect the fields. For more information about connecting to upstream object fields, see Rule Specification transformation.
  5. Verify the rule specification output fields on the
    Output Fields
    tab.
  6. You can optionally rename the Rule Specification 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.
Consider the following rules and guidelines when you use a parameter to identify the rule specification that the transformation uses:
  • If you use a parameter to identify the rule specification, you must use a parameter to define the field mappings on the
    Field Mapping
    tab. The parameter must be of type
    string
    .
  • If you use a parameter to identify the rule specification, any downstream object in the mapping that connects to the Rule Specification transformation must be completely parameterized.
If you update an asset in
Data Quality
after you add it to a transformation, you may need to synchronize the asset version in the transformation with the latest version. For more information about data quality asset synchronization, see Synchronizing data quality assets.

0 COMMENTS

We’d like to hear from you!