Informatica April 2026 Major Release: Impact on Automic IICS Taskflow Monitoring.
search cancel

Informatica April 2026 Major Release: Impact on Automic IICS Taskflow Monitoring.

book

Article ID: 437361

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine Automic SaaS

Issue/Introduction

Customers using the Automic IICS (Informatica Intelligent Cloud Services) integration to monitor taskflows may experience issues retrieving sub-task status after Informatica's April 2026 Major Release.

Specifically, taskflows may only show an overall status, or sub-tasks may fail to populate in the job report/monitoring view if the integration is not updated to meet new Informatica API requirements.

Environment

  • Component: Integration.IICS 24.0.0

Cause

Effective with the April 2026 Major Release, Informatica is updating its Taskflow Status API. While monitoring the overall taskflow status remains unchanged, Informatica now requires a specific query parameter to retrieve details for sub-tasks:

  • Required Parameter: subtaskDetails=yes
  • Example Endpoint: /active-bpel/services/tf/status?runId=<runId>&subtaskDetails=yes

Without this parameter, the API will only return the high-level completion status of the taskflow, omitting individual step/sub-task tracking.

Resolution

This compatibility requirement is being addressed via internal defect DE184680. Full support for the mandatory subtaskDetails=yes parameter is scheduled for release in:

  • Component: Integration.IICS 24.0.1 - Available

Public Title:
Support JWT and Taskflow API change

Public Description:
Supporting JWT authentication
Supporting latest behavior change of the Taskflow Status API

Additional Information

Recommendation

  1. Assess Usage: If your workflows rely on monitoring individual sub-task status within Automic, plan to upgrade your IICS integration agent.
  2. Upgrade: Once released, download and install Integration.IICS 24.0.1 to ensure continuous sub-task visibility after the Informatica April 2026 upgrade.
  3. Overall Status: If your implementation only requires confirmation of overall Taskflow completion, no immediate action is required as the default API behavior for top-level status remains unchanged.