Table of Contents

Search

  1. Preface
  2. Introduction to Informatica Data Engineering Integration
  3. Mappings
  4. Mapping Optimization
  5. Sources
  6. Targets
  7. Transformations
  8. Python Transformation
  9. Data Preview
  10. Cluster Workflows
  11. Profiles
  12. Monitoring
  13. Hierarchical Data Processing
  14. Hierarchical Data Processing Configuration
  15. Hierarchical Data Processing with Schema Changes
  16. Intelligent Structure Models
  17. Blockchain
  18. Stateful Computing
  19. Appendix A: Connections Reference
  20. Appendix B: Data Type Reference
  21. Appendix C: Function Reference

Step 1. Define Audit Rules

Step 1. Define Audit Rules

An audit rule calculates an aggregate value for a single field in either a Read transformation or a Write transformation. Each rule returns a single numeric result.
  1. In the mapping audit properties, select the
    Rules
    tab.
  2. Select the
    New (Insert)
    icon.
    The following image shows the icon: Screenshot of the Audit properties in the Developer tool. The New (insert) icon on the Rules tab is highlighted with a red circle.
    A rule appears with default values.
  3. Configure the following properties for a rule:
    Property
    Description
    Name
    Required. Name of the rule.
    Description
    Optional. Description of the rule.
    Transformation
    Required. Select a Read transformation or a Write transformation.
    Column
    Required. Port from the configured transformation to apply the rule to. You can configure a mapping parameter for the column.
    Filter
    Optional. Filter expression to apply to the column before calculating the aggregate value. The filter should return a boolean value for each row. Use transformation language to configure the filter. You can configure a mapping parameter for the filter.
    You cannot use aggregate functions in the filter.
    Type
    Required. Aggregate type to calculate. You can configure a mapping parameter for the type.
    You can use the following types for any column:
    • Count
    • Distinct Count
    • Null Count
    You can use the following types for numeric columns:
    • Average
    • Max
    • Median
    • Min
    • Percentile
    • Standard Deviation
    • Sum
    • Variance
    Execution Override
    Optional. Determines whether the Data Integration Service runs a rule before or after it runs the mapping logic.
    When
    Execution Override
    is set to
    Default
    , the Data Integration Service runs rules for the Read transformation before the mapping logic and rules for the Write transformation after the mapping logic.
    To run a Write transformation rule before the mapping logic executes, set the value to
    Pre Mapping
    . To run a Read transformation rule after the mapping logic executes, set the value to
    Post Mapping
    .
    You can configure a mapping parameter for the execution override.
For example, you can check the average value of a column in the target both before and after the mapping runs. Create two rules with the same transformation, column, and filter. Set
Type
to
Average
. Set
Execution Override
to
Default
for one rule and
Pre Mapping
for the second rule.

0 COMMENTS

We’d like to hear from you!