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 Not under consideration
Created by Guest
Created on Mar 21, 2019

Config center - Validation of MAP and TXO during deployment

In Config Center when we deploy a map by uploading the map and txo there is a risk of selecting a wrong map and txo which the sytem doesn't validate.
In such scenario the input file would process through a wrong TXO and would create issues to customer (Translation Failure as the map is processign through the diffeent TXO)

Scanario:

Assuming we have two maps with the below combination
TEST1.map and TEST1.txo
TEST2.map and TEST2.txo

During Map deployment in Config center if we select TEST1.map and TEST2.txo it doesn't validate and the map gets deployed in such cases all input files are processing through
TEST2.txo and would fail. To avoid such cases during deployment (when we click Deploy) it must validate if the Name (TEST1) is matching for the map and txo then only deploy otherwise
throw a pop-up "Either MAP or TXO is not matching"

Thank you,
Naveen

What is your industry? Other
How will this idea be used?

During Map deployment in Config center if we select TEST1.map and TEST2.txo it doesn't validate and the map gets deployed in such cases all input files are processing through
TEST2.txo and would fail. To avoid such cases during deployment (when we click Deploy) it must validate if the Name (TEST1) is matching for the map and txo then only deploy otherwise
throw a pop-up "Either MAP or TXO is not matching"

  • Guest
    May 15, 2019

    Being addressed through new self service tools