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 Delivered
Workspace API Connect
Created by Guest
Created on Sep 24, 2021

Reporting for the AMU tool used for migration v5 to v10

Following feature would help us out when we migrate from v5 to v10 and share the finding to respective team. 1.AMU tool to be able to list the products and API that would be sluggified along with the fields. 2.AMU tool to list the mapping of what was sluggified to what. For example in case of API version the provider have to know what is the version now that is getting deployed with. 3.AMU tool to provide option to sluggify without hash at the end. 4.AMU tool to list product and APIs which would have name collision if sluggified. So that we know what is the getting impacted with sluggification performed without hash.
Idea priority Urgent
  • Admin
    Nathan Ziemann
    Jan 29, 2022

    Improvements to item 1 of 4 was provided in the AMU tool for 10.0.4 and refresh of AMU tool for 10.0.1, in December 2021 time frame.

    For item 3 - we delivered a new --sluggify-no-checksum option. It comes some small caveats that may have some name collisions. For item 4, if you select the -no-checksum options and then look at the logs, you'll find the list of any name collisions now. These were added in 10.0.4 AMU and 10.0.1 AMU refresh.

  • Admin
    Nathan Ziemann
    Nov 15, 2021

    This RFE will address item 3 of 4 providing a new option --sluggify-no-checksum. Item 4 of 4 won't provide a tool that provides a list specifically, but we will log the names during unpack, so when using the new no-checksum option, the log can be reviewed to get the list.

    Items 1 and 2 should be created in separate RFEs in order to consider them in the future.

    Additionally, we are reducing characters that are sluggified, so the list will be shorter in the future. This includes APIs with "." or "_" will not be sluggified.

  • Admin
    Nathan Ziemann
    Nov 11, 2021

    Moving to in development. A subset of the four separate enhancements listed above will be improved upon. A summary statement will be provided later that describes which will be improved.