includes the following new features and enhancements in this release.
CLAIRE-powered runtime strategies
CLAIRE-powered runtime strategies include the following new features and enhancements:
Mapping
tasks use a new layout to display runtime strategies. The option to enable or disable runtime strategies was replaced by an option to run the task using the default runtime strategy.
CLAIRE can recommend runtime strategies for
mapping
tasks that run in Databricks Delta ecosystems. The
mapping
task must be based on a mapping in advanced mode.
For more information, see
Tasks
.
Expression transformation field types
When you have a long list of types and want to see the type for each expression field, add the
Field Type
column in the Expression properties table.
Generate a single output in the Hierarchy Builder transformation
You can configure a Hierarchy Builder transformation to group all of the output elements in a single output group.
Start REST API session using JWT access token
You can start a new REST API session by logging in using a JWT access token for authentication. To log in, use the loginOauth v2 REST API resource and include a token from the identity provider in the request.
For more information, see REST API Reference.
Update dynamic cache condition
When a Lookup transformation uses a dynamic lookup cache, you can configure a conditional expression to tell
Data Integration
when to update the cache.
Data Integration
updates the cache when the expression is true.
For more information about configuring Lookup transformations, see
Transformations
.
User-defined functions supported in advanced mode
You can include user-defined functions in the following transformations in advanced mode:
Aggregator
Expression
Availability of human task assets in Data Integration Bundles
When you create a bundle in Data Integration, you can include human task assets. The users can use the bundles for various
Informatica Intelligent Cloud Services
projects.
Taskflows
Taskflows include the following new features and enhancements:
You can use an API to terminate up to 200 taskflows. Use the following URI to terminate multiple taskflows:
PUT <Informatica Intelligent Cloud Services URL>/active-bpel/services/tf/terminate
Enter the taskflow run IDs as the input in the body of the PUT request. The API supports basic authentication and session ID authorization.
For more information about terminating multiple taskflows, see
Taskflows
.
You can use a JLS API to get a list of up to 200 taskflows that are suspended. Use the following URI to get the list of suspended taskflows:
{{<Informatica Intelligent Cloud Services URL>}}/jls-di/api/v1/Orgs(<Organization ID>)/JobLogEntries?$top=<Number of suspended taskflows>&$filter=(status eq 'SUSPENDED' and assetType eq 'TASKFLOW')
Use the following URI to get the list of the latest suspended taskflows in an organization filtered by user:
{{<Informatica Intelligent Cloud Services URL>}}/jls-di/api/v1/Orgs(<Organization ID>)/JobLogEntries?$top=<Number of suspended taskflows>&$filter=(status eq 'SUSPENDED' and startedBy eq '<username>' and assetType eq 'TASKFLOW')
By default, the number of suspended taskflows that the API returns is 200.
For more information about getting the list of suspended taskflows, see
Taskflows
.
You can add a custom name to a taskflow by using an API and the RunAJob utility. You can use the custom name as an identifier for the taskflow.
For more information about adding a custom name to a taskflow, see
Taskflows
.
You can view the metering information for the taskflows that are run within your organization and sub-organizations on the
Metering
page of Administrator. You can also download metering usage data from the taskflow metering page. The metering page includes details such as the date when the taskflows within the organization were run, organization ID, organization type, environment name, environment type, tier, IPU per unit, total number of taskflows that were run, and the number of IPUs consumed.