Table of Contents

Search

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