Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software 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.

Status Not under consideration
Workspace z/OS Connect
Created by Guest
Created on Dec 19, 2019

Support for character escaping in API requester scenario

To call some services we are required to avoid certain characters, such as the comma and such, which may exist in the COBOL input strings, and replace them in the JSON by standard symbols such as ' .
We thought of using an interceptor to do this, but found none were applicable.

Idea priority High
  • Guest
    Reply
    |
    Jan 16, 2020

    This requirement has been evaluated. It is not our intention to provide input validation within API Requester. This should be done using an API Gateway (API Connect or Data Power) and/or within the application logic of the app that is the target for the API call. This requirement is therefore being rejected. You have an opportunity to resubmit in twelve months time if you wish it to be considered then.