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.

Add a new idea Subscribe
Status Not under consideration
Workspace z/OS Connect
Created by Guest
Created on Jun 30, 2023

RELATED IDEAS

Enable z/OS Connect API Requester Feature to Transparently handle API Endpoint changesEnable z/OS Connect API Requester Feature to Transparently handle API Endpoint changes

Enable z/OS Connect API Requester Feature to Transparently handle API Endpoint changesCurrently, when an API endpoint has new response fields added that an API Consumer does not need, z/OS Connect API Requester will start to fail unless its API Requester Archive (ARA) is updated so its definition of the API includes the new fields (even though the consumer does not need them)


Standards for RESTful API development require that API Consumers tolerate non-impactful changes. Adding new properties in a response is considered a non-impactful change.


If z/OS connect could manage receiving a response structure that contains fields that are not defined in the ARA, then it would simplify coordinating the rollout of API changes with all consumers of the API (ie no need to tightly coordinate the rollout of the API changes and implement the new ARA file at the same time in all locations).


This Idea had been submitted previously and had 13 votes at that time.

Idea priority High
  • Guest
    Reply
    |     Jul 3, 2023

    Hello,

    Thank you for raising this Idea. As this capability has been delivered in our OpenAPI 3 support, it is not likely that support for this in OpenAPI 2 would be implemented in future z/OS Connect releases. Consequently, this requirement is being declined. You have an opportunity to resubmit in twelve months time if you still wish it to be considered.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.