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 Future consideration
Workspace IBM Turbonomic ARM
Categories General/Other
Created by Guest
Created on Jun 4, 2026

Add automatic variables to Workflow content templates

Add "automatic variables" (Velocity variables, similar to $action, but maybe $turbo) to Workflow content templates that would provide:

  • the name of the policy that fired the workflow
  • the execution step of the policy that fired the webhook
  • the name of the workflow that generated the webhook
  • any other Turbo metadata that would be useful

If these were provided to the template as Velocity variables, it would allow you to include those in the webhook payload. Probably not useful for the target system, but it could be very useful if you need to do any debugging (especially if one workflow is attached to multiple policies)

Something like:

  • $turbo.Policy                                (name of the policy that fired the workflow)
  • $turbo.PolicyExecutionStep     (onGeneration|beforeExecution|onExecution|afterExecution)
  • $turbo.Workflow                         (name of the workflow that fired the webhook)
Idea priority Low