Table of Contents

Search

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

Transformations

Transformations

Rule Specification transformation

Rule Specification transformation

The Rule Specification transformation adds a rule specification asset that you created in
Data Quality
to a mapping.
A rule specification is a set of one or more logical operations that analyze data according to business criteria that you define. The rule specification generates an output that indicates whether the data satisfies the business criteria. The rule specification can also update the data that it analyzes. You define the logical operations as IF/THEN/ELSE statements in
Data Quality
.
Each Rule Specification transformation can contain a single rule specification. You can add multiple Rule Specification transformations to a mapping.
Use a Rule Specification transformation to accomplish the following goals:
  • Define the types of data that a business data set contains.
  • Define a set of conditions that the business data must satisfy.
  • Define the actions to take when the data satisfies the conditions of the business rule.
  • Define the actions to take when the data fails to satisfy the conditions of the business rule.
A Rule Specification transformation is similar to a Mapplet transformation, as it allows you to add data analysis and data transformation logic that you designed elsewhere to a mapping. Like mapplets, rule specifications are reusable assets. A Rule Specification transformation shows incoming and outgoing fields. It does not display the logic that the rule specification contains or allow to you edit the rule specification. To edit the rule specification, open it in
Data Quality
.
To use the Rule Specification transformation, you need the appropriate license.

0 COMMENTS

We’d like to hear from you!