Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Table of Contents

Search

  1. Preface
  2. Introduction to rule specifications
  3. Rule specification configuration
  4. Rule set configuration
  5. Rule statement configuration
  6. REST APIs for rule specifications
  7. Rule specification configuration in advanced mode
  8. Business rules and rule statements
  9. Validation and testing

Rule specification assets

Rule specification assets

Rules and guidelines for mapplets in conditions and actions

Rules and guidelines for mapplets in conditions and actions

You can optionally add a mapplet to a function in a rule statement condition or action. When you add a mapplet, you add the logic of any asset or transformation in the mapplet to the condition or action.
The mapplet can contain any passive data quality transformation and can additionally contain a passive Java transformation and Expression transformation.
Consider the following rules and guidelines when you add a mapplet to a condition or action:

Passive transformations

You can use the following transformations in a mapplet that you add to a condition or action:
  • Parse transformation
  • Cleanse transformation
  • Labeler transformation
  • Rule specification transformation
  • Verifier transformation
  • Expression transformation
  • Java transformation in passive mode
Do not define an in-out parameter on a mapplet that you add to a condition or action. Before you add a mapplet with a Java transformation to a condition or action, compile the transformation in Data Integration.
For information about how to use a Java transformation that consumes external Java packages in a mapplet, see the Knowledge Base article KB 000227229.

Nested mapplets

You can configure a condition or action with up to four nested mapplets and rule specification assets in an alternating manner.
Consider the following example:
  • You select the Mapplet function in a condition.
  • You configure the condition to read a mapplet that contains a Rule Specification transformation named
    RuleSpec1
    .
  • The Rule Specification transformation reads a rule specification asset with a condition that also specifies a Mapplet function.
  • The mapplet that you specify in this condition contains a Rule Specification transformation named
    RuleSpec2
    , which reads an additional rule specification asset.
In this way, you can create four levels of mapplets and rule specifications beneath a condition or action.

0 COMMENTS

We’d like to hear from you!
Sergio Moreno - February 20, 2024

Good afternoon,

I wanted to clarify a doubt. If I understand correctly in a Mapplet that is going to be included later inside a Rule Specificiation there could not be a LookUp functionality, only the functions specified in the "Passive transformation" section. I am trying to make a quality rule that involves two tables by means of a Mapplet inside a Rule Specification. If this is not possible, is there any way to make a quality rule that involves fields from different tables

Thank you very much.

Sergio

Informatica Documentation Team - February 21, 2024

Hi Sergio,

We’d like to get some more information about your comment. Can you tell us what your objective is?

Thanks,

Informatica Documentation Team


Sergio Moreno - February 22, 2024

Good afternoon,

What we want to achieve is to make a quality rule involving two fields from two different tables. For example, we want to corroborate that field A of table A is the same as field B of table B. We want to achieve this without the need to do a Join as this would involve adding the fields to be checked in a new table or creating a Mapplet scan in Data Profiling.

Thank you.

Sergio


Informatica Documentation Team - February 23, 2024

Hi Sergio,
We plan to introduce documentation for this use case for rule specifications in an upcoming release. Meanwhile, we recommend that you contact Global Customer Support for assistance.
Thanks,
Informatica Documentation Team



Prasuna Gillela - May 08, 2024

Hello,

 

Can we create rules without mapplets ?

Informatica Documentation Team - May 10, 2024

Hi Prasuna Gillela,
Yes, you can create a rule specification without a mapplet. A mapplet is an optional element in a rule specification. We’ve updated the page you referenced to make this clearer.
Thanks,
Informatica Documentation Team


Prasuna Gillela - May 10, 2024

Thank you.