When running a mapping that includes an Access Policy transformation in

Data Integration

, an error occurs if the transformation includes a

data filter policy

that uses any of the following operators on a date data type:

is any of
is greater than
is greater than or equal to
is less than
is less than or equal to
is none of

No error occurs if the

data filter policy

uses any of the following operators on a date data type:

is null
is not null

After you create a mapping that includes an Access Policy transformation in

Data Integration

, if you add parameters in the source, this change is not reflected in the output.

When you parse a PDF document that contains tables created in Microsoft Excel, Intelligent Structure Discovery doesn't detect the data correctly.

When you use an intelligent structure model in a Structure Parser transformation to read a PDF document, even though the mapping correctly writes to the target, the session log displays the following error:

When you use the pullByCommitHash REST API resource to pull objects from a project-level repository, an error occurs even if you pass the repoConnectionId field.

When you parameterize the lookup expression for an unconnected Lookup transformation in a mapping in SQL ELT mode, and the expression passes an integer or decimal value, the mapping task displays a validation error saying that the argument data types aren't valid.

When you run a mapping with a Structure Parser transformation that uses an intelligent structure model based on a Cobol copybook, the output is incorrect if the mapping processes a DAT file.

Tag names can't include control characters or certain special characters. However, when you create a tag, no warning is displayed when the tag name contains a control character or the following special characters: ? ' | { } " ^ & [ ] /

When you use an intelligent structure model based on a Cobol copybook in a Structure Parser transformation, the output file is invalid if the transformation processes file types other than binary files.

The

My Jobs

page in

Data Integration

and the

All Jobs

and

Running Jobs

pages in

Monitor

display the taskflow start time and end time values based on the time zone setting in the user profile. However, when you open a taskflow instance, the values in the

Start time

and

End time

fields appear in Coordinated Universal Time (UTC) regardless of the time zone setting in the user profile.