Skip to Main Content

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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace App Connect
Created by Guest
Created on Mar 18, 2024

Allow emiting monitoring events from non connected node terminals

Currently in order to let a flow in ACE emit a business monitoring event through a node terminal, this terminal needs to be wired to a downstream node, otherwise it is ignored. The consequence is that terminals that you want to monitor, usually (but not only) failure and error terminals, need to be wired with the issue that by wiring a failure terminal you change the final state of the flow from error to success which mess up with error handling and like transactions.

The solution is to wire to a throw node forcing the final flow status to error. However this approach generates unnecessary cramped flows that are difficult to follow and maintain. If your original flow had a certain complexity with multiple branches inputs and outputs this leads to increasingly busy flows with very difficult to setup error handling.

If we could just emit business monitoring events through unwired node terminals the resulting flows would be way cleaner and easier to maintain and develop. The failure/error condition is obtained anyway either if the terminal is wired or not, so it would only make sense that we could capture that status without modifying the logic of our flow.

Idea priority Medium
  • Admin
    Ben Thompson
    May 3, 2024

    Idea Review. Thank you for taking the time to raise this request. In its current form we are rejecting this request, but we are open to further discussion for how to best achieve your use-case either by adopting an alternative flow design with the product in its current form, or through a different enhancement suggestion which meets your aims in a slightly different way. To help explain our position ...

    We feel it would be very confusing to users if events were emitted from a terminal which had never actually been fired by a message flow. From a flow control point of view, this could result in monitoring messages coming from one terminal but the main data flowing to a different terminal. This would lead to confusion about whether an exception had actually been thrown and rolled back, or whether it had been caught and handled. The proposal could also cause fundamental difficulties for other product implementations such as Business Transaction Monitoring which are based on top of the flow monitoring architecture. With BTM, monitoring events are used to assign status of the transaction as either started/inprogress/failed. Allowing this feature would mean that a BTM transaction could be assigned a status due to an event being published from a different route to the direction the message actually flowed.

    Given these concerns, unfortunately on this occasion we will not be pursuing this idea further in its current form.