Integration
Hide about this portal


This is an IBM Automation portal for Integration 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 Future consideration
Workspace App Connect
Created by Guest
Created on Jun 1, 2023

RELATED IDEAS

HTTPInput and HTTPRequest nodes should have the option to set the Message Parsing to use the HTTP Header ContentType

See this idea on ideas.ibm.com

HTTPInput and HTTPRequest nodes should have the option to set Message Parsing to use the HTTP Header ContentType

So if it gets Content-Type=application/xml it uses the XMLNSC parser and if it gets Content_Type=application/json it uses the JSON parser

This will permit users to send messages built in different wire formats but with the same logical content to ACE without having to set the Message Parser to BLOB and then determine which parser to use in subsequent code.

It will also help with situations where a Gateway or other intermediate code sends back HTML for errors but the expected JSON or XML for positive path responses.

Idea priority Medium
  • Admin
    Ben Thompson
    Reply
    |     Jun 16, 2023

    Thank you for taking the time to make this suggestion. We agree that using the Content-Type field to dynamically infer a desired parser for the message body would be a valuable addition to the product for some use cases ... In fact when adding the RESTRequest node to the product we took a similar approach and added checkboxes to that node's properties. The same approach could be applied as an option to the HTTPInput and HTTPRequest. Status is updated to Future Consideration.

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.