Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Data Integration
  • All Products

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. 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 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

Back Next

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!