New features and enhancements

You can configure custom row delimiters in Source and Lookup transformations.

For more information, see Transformations

When you create a flat file target at run time, you can configure the target field order. When you run the task, Data Integration writes fields to the target in the order that you specify.

For more information about configuring target fields, see Transformations.

When you view job details for a mapping task or dynamic mapping task, success row information is now available for Amazon S3 V2, Google Cloud Storage V2, and Microsoft Azure Data Lake Storage Gen2 connections.

When you create a custom or advanced relationship to join objects in a Source transformation with an Oracle or SQL Server connection, you can join objects from different schemas.

For more information, see Transformations.

If a Target transformation uses update or upsert as the target operation, the Task Details page for the mapping task displays the update columns. Previously, you needed to edit the mapping task to view the update columns.

For more information, see Tasks.

You can define a mapping that includes different target connections when the only difference in the object names is the case. For example, you can define a Target transformation to use an Oracle connection with the object name Sample_Table, and another Target transformation to use a Snowflake connection with the object name sample_table. Previously, the object names could only be the same if they used the same case.

For more information, see Transformations.

When you use a flat file connection in a Source, Lookup, or Target transformation, you can use a file on your local machine to generate field metadata. You can generate field metadata from a local file for single object and command sources and for single object targets and lookups.

For more information, see Transformations.

You can configure a mapping to preserve some special characters in the source and target field names. When the mapping preserves special characters, the source and target field names can include any character except the following characters: . + - = ~ ` ! $ % ^ & * ( ) [ ] { } ' \ " ; : / ? , < > | \t \r \n

The mapping replaces the listed characters with an underscore (_). Previously, the mapping replaced all characters except alphanumeric characters and underscores.

For more information, see Mappings.

Taskflows use TLS version 1.3 as the protocol to encrypt communications between the clients and servers on the Informatica Cloud Server. It ensures confidentiality and integrity of the data that is transmitted across a connection. TLS version 1.3 offers a faster TLS handshake and secure cipher suites.

For more information, see Introduction.