Skip to Main Content
IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. 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.

Status Delivered
Categories Maps & Type Trees
Created by Guest
Created on Nov 27, 2023

ITX - Extend validation exception handling for messages with a known structure BUT an unknown (as more recent) version

Currently ITX FinPay routing map identifies a messages based on the tag <FIToFICstmrCdtTrf> in Document and not based on message name and its version (pacs.008.001.08).  This causes a problem when a message based on a more recent version is received.

e.g. in case of pacs.008.001.12, routing map identifies run map based on <FIToFICstmrCdtTrf> tag and routes it to cbpr6303_pacs_008_001_08.  In run map, as the schema used for input card is pacs.008.001.08, the message does not parse the input card as message is pacs.008.001.12 and hence a generic error "MAP FAILED(8) One or more inputs was invalid" is logged.