Skip to Main Content
Cloud Management and AIOps
Hide about this portal


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps 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.

Provide manual sorting order for matchTokens values entered into a rule via the UI

See this idea on ideas.ibm.com

matchTokens processing on event reception halts after the first resource matching a token is found. This provides an implicit ordering of token values to be entered from most-specific to most-generic. Achieving this is trivial when creating matchToken values via e.g. the File Observer by specifying the values in the desired order.

However, values entered into the "Tokens" multi-entry box when defining a matchTokens rule in the User Interface are automatically sorted into alphabetical order, and the actual values of the matchToken strings produced is in the sorted value order, which overrides the ability to impose any specific ordering. This behaviour appears not to be override-able.

Either prevent the automatic sorting of entered field values (accepting them in entered order) or provide a manual sorting order after entry (drag and dropping values?) to allow for the same flexibility in user control of matchTokens order as can be achieved when specifying the value order when submitting topology via Observers. 

Idea priority Low