Skip to Main Content

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:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portal, please send email describing the issue to for resolution. For more information about IBM's Ideas program visit

Status Future consideration
Workspace App Connect
Created by Guest
Created on May 11, 2022

Possibility to choose a MQ Policy for Timeout nodes & Co

Currently, it is only possible to use the default remote Queue Manager.

I would like to be able to choose my MQ Policy at the design time or during the deploy, as MQ Nodes

Idea priority Medium
  • Admin
    Ben Thompson
    May 11, 2022

    RFE Review. Thank you for taking the time to submit this idea for enhancement. As highlighted, it is possible to direct the Timeout nodes to use a remote queue manager through changing the default remote queue manager setting in the server.conf.yaml file. A new setting in the Timeout policy itself, or via a pointer from a Timeout policy to an MQEndpoint policy, would enable this configuration to be become more dynamic (changeable through policy redeploy rather than through server restart). Status of the suggestion is updated to Future Consideration.