Informatica Intelligent Cloud ServicesData Integration includes the following changed behaviors in this release.
Job details for mappings in SQL ELT mode
When you run a mapping in SQL ELT mode, the job details page shows the individual target results for each target in the job.
Previously, the job details page showed only one target and the number of target rows shown was cumulative for all targets in the mapping.
For more information about viewing job results, see Monitor.
SQL ELT query preview
When you preview the SQL query for a mapping that uses SQL ELT optimization, the query panel is renamed to SQL ELT Query, and the button that you click to generate the query is labeled Generate SQL Query as shown in the following image:
Previously, the panel was named SQL ELT Optimization, and the button was labeled SQL ELT Preview.
For more information about previewing SQL ELT queries for mappings, see Mappings.
Rounding for double data type values
For double data type source fields that are connected to a downstream decimal or string data type field, Data Integration retains digits beyond the 15th digit.
Previously, Data Integration rounded all double data type values to the 15th digit.
For more information about double data types, see Function Reference.
Taskflows
Taskflows include the following changed behaviors:
•In a Data Task step that you use to add a mapping task, the Path column corresponding to the in-out parameters in the input and output fields includes the mapping task ID. Previously, the Path column included only the mapping task name and not the mapping task ID.
Note: A taskflow that uses mapping tasks with the same name but different in-out parameters becomes invalid. You must re-select the mapping tasks in the taskflow to fix the issue. However, the taskflow will still run successfully even if it shows up as invalid.
• In a subtaskflow, when a Data Task step that uses a mapping task fails, and you select the Subtaskflow step in the taskflow instance from the All Jobs or My Jobs page, the Source section on the Fault tab displays the subtaskflow name followed by the mapping task name that failed.
If a subtaskflow containing multiple Data Task steps fails, the Source section on the Fault tab displays the subtaskflow name followed by the mapping task name of the first Data Task step that failed.
With this change, you can easily identify issues with the subtaskflow and mapping task.
The following image shows the subtaskflow name and the mapping name in the Source section on the Fault tab:
Previously, in a subtaskflow, when a Data Task step with a mapping task failed, the XPath for the subtaskflow was displayed in the Source section on the Fault tab, which was not useful.
The following image shows the XPath of the subtaskflow in the Source section on the Fault tab:
