Transformations
This section describes new transformation features in version 10.0.
Informatica Transformations
This section describes new features in Informatica transformation in version 10.0.
Address Validator Transformation
Effective in version 10.0, you can define parameters to set the following transformation properties:
- •Geocode data type
- •Global Max Field Length
- •Max Result Count
- •Optimization Level
- •Standardize Invalid Address
For more information, see the "Address Validator Transformation" chapter in the Informatica 10.0 Developer Transformation Guide.
Bad Record Exception Transformation
Effective in version 10.0, you can use parameters to specify the upper threshold and the lower threshold that the transformation uses to identify bad records.
For more information, see the "Mapping Parameters" chapter of the Informatica 10.0 Developer Mapping Guide.
Data Processor Transformation
This section describes new Data Processor transformation features.
Data Transformation Libraries
Data Transformation libraries contain predefined transformation components for a range of industry messaging standards. The Data Processor transformation uses a Library object to transform an industry messaging type input into a different format, such as an XML output document, or from an XML input to an industry message output.
The Library object contains many objects and components, such as Parsers, Serializers, and XML schemas, preset to transform the industry standard input and specific application messages into XML or other output. Some libraries contain additional objects for message validation, acknowledgments, and diagnostic displays. You can also customize the properties and validation settings of the Library object.
You can create Library objects for the DTCC-NTCC, EDIFACT, EDI-X12, HIPAA, HL7, and SWIFT libraries.
For more information, see the Informatica Data Transformation 10.0 User Guide and the Informatica Data Transformation 10.0 Libraries Guide.
Complex File Reader without a Streamer
You can use the Complex File Reader without a Streamer as the start-up component in a Data Processor transformation that receives the input.
For more information, see the Informatica Data Transformation 10.0 User Guide.
Pass-Through Ports with Custom Data Types
Data Processor transformations can include pass-through ports with custom data types.
For more information about custom data types, see the Informatica Developer 10.0 User Guide.
RunMapplet Statement for XMap
You can define a RunMapplet mapping statement to call a mapplet from an XMap in a Data Processor transformation. One or more MappletInput and MappletOutput statements can be nested under the RunMapplet statement. Values are mapped to the mapplet input ports in the same order that they are listed in the MappletInput statements. The values in the mapplet outlet ports are mapped to the MappletOutput statement in the same order that they are listed in the mapplet ports.
For more information, see the Informatica Data Transformation 10.0 User Guide.
Script Mode Editing
You can edit a Script for the Data Processor transformation with an external editor. For example, you can perform a global find and replace operation with an external editor.
For more information, see the Informatica Data Transformation 10.0 User Guide.
Decision Transformation
Effective in version 10.0, you can use parameters to specify input values in a Decision transformation script.
For more information, see the "Mapping Parameters" chapter of the Informatica 10.0 Developer Mapping Guide.
Duplicate Record Exception Transformation
Effective in version 10.0, you can use parameters to specify the upper threshold and the lower threshold that the transformation uses to identify duplicate records.
For more information, see the "Mapping Parameters" chapter of the Informatica 10.0 Developer Mapping Guide.
Expression Transformation
This section describes the new features in the Expression transformation.
- Dynamic Expressions
Effective in version 10.0, you can create an expression in a dynamic output port. When you create an expression in a dynamic port, the expression is a dynamic expression. A dynamic expression might generate more than one output port when the expression contains a port selector or a dynamic port. When the dynamic expression runs against multiple ports, the expression returns an output value for each port.
For more information about dynamic expressions, see the Expression Transformations chapter in the Informatica 10.0 Developer Transformation Guide.
- Mapping Outputs
Effective in version 10.0, you can configure mapping outputs. A mapping output is a single value that is the result of aggregating a field or expression from each row that the mapping processes. For example, a mapping output can summarize the total amount of an order field from all the source rows that the transformation receives. A mapping output expression is a field value or an expression to aggregate from the rows that the Expression transformation receives. You must define a mapping output in the mapping Properties view, before you can create the corresponding expression in the Expression transformation.
For more information about mapping outputs, see the Mapping Outputs chapter in the Informatica 10.0 Developer Mapping Guide.
- Test Expressions
Effective in version 10.0, you can test expressions that you configure in the Expression Editor. When you test an expression, you enter sample data and then evaluate the expression.
You can test expressions when you configure expressions in the following ways:
- - In an output or variable port in the Expression transformation
- - In the Mapping Outputs view of an Expression transformation after adding the transformation to a mapping
The following image shows the results of an expression that concatenates a sample first name and last name:
For more information about testing expressions, see the "Expression Transformation" chapter in the Informatica 10.0 Developer Transformation Guide.
Hierarchical to Relational Transformation
This section describes the Hierarchical to Relational transformation that you create in the Developer tool.
The Hierarchical to Relational transformation is an optimized transformation introduced in version 10.0 that converts hierarchical input to relational output.
For more information, see the Informatica 10.0 Developer Transformation Guide.
Match Transformation
Match Type Options in Identity Match Analysis
Effective in version 10.0, you can select the following options when you configure the Match transformation to read a persistent store of identity index data:
- Remove IDs from the database
- The transformation deletes rows from the index tables if the rows share sequence identifiers with rows in the mapping source data. The transformation does not perform match analysis when you select the option.
- Update the current IDs in the database
- The transformation replaces rows in the index tables with rows from the mapping source data if the rows share sequence identifiers. The transformation does not add rows to the index. The transformation can include the rows that it does not add in the match analysis.
For more information, see the "Match Transformations in Identity Analysis" chapter of the Informatica 10.0 Developer Transformation Guide.
Matching Process Options in Identity Match Analysis
Effective in version 10.0, you can enable and disable match analysis when you configure the transformation to update a persistent store of identity index data. Use the Matching Process option to enable or disable match analysis.
For more information, see the "Match Transformations in Identity Analysis" chapter of the Informatica 10.0 Developer Transformation Guide.
Status Codes for Identity Analysis with an Persistent Index Store
Effective in version 10.0, the Match transformation can generate the following status codes to describe the results of match analysis on a persistent index data store:
- Absent
- The index data store does not contain data for the current record.
- Invalid
- The transformation cannot analyze the current record. For example, the transformation cannot generate index data for the record because the key field on the Match Type tab is not compatible with the record data.
- Removed
- The transformation removes the index data for the record from the index data store.
- Updated
- The transformation updates the rows in the persistent data store with index data from the transformation input record. The transformation input data and the persistent index data have common sequence identifiers.
For more information, see the "Match Transformation" chapter of the Informatica 10.0 Developer Transformation Guide.
Parameter Usage
Effective in version 10.0, you can use parameters to set the following options on the Match transformation:
- •The match score threshold value.
- •The relative weight that the transformation applies to the scores from each match strategy.
- •The persistence method that the transformation applies to the persistent index data store in identity match analysis.
For more information, see the "Mapping Parameters" chapter of the Informatica 10.0 Developer Mapping Guide.
Sequence ID Port
Effective in version 10.0, the Match transformation output ports include a Sequence ID port when you configure the transformation to read a persistent index store. The transformation uses the sequence identifier values to track the index data through the different stages of the match analysis.
For more information, see the "Match Transformation" chapter of the Informatica 10.0 Developer Transformation Guide.
SQL Transformation
This section describes new features in the SQL transformation.
Effective in version 10.0, you can parameterize the connection for an SQL transformation. Define the parameter in the mapping. Then, assign the parameter to the Connection Name in the SQL transformation run-time properties.
For more information, see the SQL Transformation chapter in the Informatica 10.0 Transformation Guide.
Transformations in Dynamic Mappings
This section describes new features in the transformations for dynamic mappings.
Effective in version 10.0, you can add dynamic ports to some transformations. You can also parameterize which input ports to link to ports from an upstream transformation. You can configure port selectors to reference multiple ports in transformation logic.
The transformations contain the following new tabs in the Properties view:
- Group By
- The Aggregator transformation, the Rank transformation, and the Sorter transformation require that you configure groups of ports. You can now configure the groups on a Group By tab. You can define groups by selecting ports or you can configure parameters that contain port lists. The Group By tab provides flexibility when you configure the transformations with generated ports.
- Port Selector
- You can reference multiple ports in transformation logic. Define a port selector, which is an ordered list of ports. You can use reference port selectors in dynamic expressions, join conditions, or lookup conditions. When you define a port selector, you can include or exclude transformation ports based on the port name, the port type, or a pattern of text characters.
- Run-time Linking
- When you configure transformations in a dynamic mapping, you can set parameters or link policies that determine which ports to link between transformations. Configure run-time linking to link dynamic ports to static ports. You can configure a link policy to link ports by name. You can configure an InputLinkSet parameter to specify the names of the of ports to link at run time.
For more information, see the Informatica 10.0 Transformation Guide.
