Skip to Main Content
Cloud Platform

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 portals, please send email describing the issue to for resolution.

For more information about IBM's Ideas program visit

Status Future consideration
Workspace UrbanCode
Categories Deploy
Created by Guest
Created on Jan 24, 2019

Make IIS Config & IIS AppCmd plugins compatible with each other

We are using IIS Configuration plug in version 10.918427 to auto discover our IIS WebServer properties. We are also using IIS AppCmd 2.423623 for deployments. There are several process steps in the AppCmd plug in that have a default Command Path set to ${p:resource/appcmd.commandPath} yet that property is not discovered by the IIS Configuration discovery. It returns a property called iis.appCmdFile but it resolves to the AppCmd file location instead of just the path. It would be very nice if these plug ins could be configured to work together with the IIS Configuration plug in returning a property value to the appcmd path that the steps in the IIS AppCmd can be set to as default.

Idea priority Medium
RFE ID 129302
RFE Product UrbanCode Deploy
  • Guest
    Feb 8, 2019

    Although the theme of this request is consistent with our business strategy, it is not committed to the release that is currently under development.

  • Guest
    Jan 24, 2019

    Attachment (Description)