Skip to Main Content
Cloud and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Under review
Created by Guest
Created on Sep 2, 2026

Enable Service Composer to expose values exported by an Ansible Job Template activity (via set_stats artifacts) as linkable output parameters for downstream activities, matching the existing behavior of Terraform and Helm activities.

Description:
In Service Composer (IBM Cloud Pak for AIOps 4.11.1, Infrastructure Automation), only Terraform and Helm activities publish output parameters that can be linked to downstream activities. The Ansible Job Template activity has input parameters only; values a playbook exports via set_stats are returned by AAP as the job's artifacts object but are never captured into the service context, so no expression can consume them in a later activity.

Request:
Capture the AAP job artifacts object as read-only output parameters of the Ansible Job Template activity, visible in the Parameters tab and available through Link Parameters for downstream activities, consistent with existing Terraform/Helm output linking.

Use case:
Sequential Ansible job templates in one service: Node 1 retrieves data and exports it with set_stats; Node 2 receives it as an extra variable.

Workaround and limitation:
Combining templates into an AAP workflow job template launched from Service Composer. This requires a dedicated workflow for every template combination, producing an unmanageable number of templates and moving orchestration logic out of Service Composer.

Idea priority Urgent