Integration


This is an IBM Automation portal for Integration 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.


Add a new idea Subscribe
Status Submitted
Workspace webMethods Integration SaaS
Created by Guest
Created on Sep 12, 2025

RELATED IDEAS

Improvement of the Logging system. (Flow/LogCustomMessage)

We would like to have more logs when needed. And we'd like to choose which logs to see, at execution time.

I can think of a similar logging system like in any other programming language, where we can have different levels of criticality: debug, log, info, warning, error, critical... Or you can simple put some levels from 1 to 6.

All flow services and workflows can have a default (and "persistent") parameter (that user should not have to create each time): "debug" or "verbose" or "logLevel", and by default should be set to "info" or "3".

At build time, the same old Flow/LogCustomMessage built-in service, or a new similar one, would allow user to choose a logging level for it.

At run time, the user can choose to run the flow with default value for the new "persistent" parameter, or to provide new one (higher or lower). If the value of the "logLevel" parameter is equal or higher with the "logLevel" of the LogCustomMessage, the message will be logged.

Basically will help us to reduce the number of "if" statements (see the uploaded picture)

Benefits:
- lower number of steps -> increased speed
- shorter flows that are easier to debug
- reduce the logging when not needed - less resource usage
- easier debugging for specific moments

Captura de pant...
Captura de pantalla 2025-09-12 184752.png
Open full size
Captura de pantalla 2025-09-12 184752.png
Idea priority Medium

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.