Skip to Main Content
Cloud Platform


This is an IBM Automation portal for Cloud Platform 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 Future consideration
Created by Guest
Created on May 17, 2019

Filter and validate option in stub needs to be configurable

Currently when we record HTTP events and create a stub, automatically all the fields gets enabled with filter condition and if there are some optional fields or we want to validate some fields instead of filter, it is really difficult especially if the payload is very big.

Idea priority Urgent
RFE ID 133040
RFE URL
RFE Product Rational Test Workbench
  • Guest
    Reply
    |
    Oct 16, 2019

    Although the theme of this request is consistent with our business strategy, it is not committed to the release that is currently under development.

  • Guest
    Reply
    |
    May 29, 2019

    Hi,

    Based on the payload, we want to decide whether we should enable filter on parent or validate specific field, at present all the XML elements are added as filter and assuming we want to implement regular expressions etc and if the payload is bigger, it takes really long time to make the changes.

    If we have an editor which the complete xml properly and if there is an option to enable filter/validate, it will reduce our operational efforts.

    Regards,
    Mahesh

  • Guest
    Reply
    |
    May 28, 2019

    We will be looking at ways we can make editing messages less opinionated, which will help with working with optional fields, large message payloads, etc.

    In terms of the request to make it easier to validate an incoming message for a stub, could you please share the use case for this?