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 Submitted
Created by Guest
Created on Sep 12, 2025

Preserve text as text and Booleans as Booleans

We received the following XML:
<CAD05><false</CAD05>

The XML is defined as a "string" in the XML Schema. We output this to JSON to a field also defined as "string" in the JSON Schema. Yet, even with TEXT() or PACKAGE() calls the output always comes as:
"E_CAD05" : false

This is a boolean, and thus the JSON output violates the JSON Schema that we used to build the ITX map with.
This even happen with an explicit ="false" definition.

Because of the way this seems to happen as a post translation process even when the map is designed and typed 100% correct, any supplier input into a free-form text field that contains either "false" or "true" breaks our output.

IMPORTANT NOTE: There is nothing that seems to be modifiable in the map that gets the output to be treated like text again without looking specifically for these two values "true" and "false" in EVERY end user enterable free-form text field, which is quite impractical.

For a platform built on strong typing, this seems to break the mold.