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 Planned for future release
Workspace webMethods Integration SaaS
Created by Guest
Created on Feb 17, 2025

RELATED IDEAS

Make document types generated for (SOAP/REST) API flow services I/O reusable in other flow services

See this idea on ideas.ibm.com

Hi,

When creating SOAP or REST APIs also empty implementation flow services are created with populated "I/O" for inputs and outputs. These are based on the WSDLs or API specifications provided.

The inputs/outputs are defined directly in the empty API implementation flow service, but it would make more sense to create document references for them and refer those in the "I/O" of the flow services for the APIs. Then these can be (re)used in other flow services used during the implementation of functionality. For each type of input, output or error of an API a document reference option.

They could be for example referenced with the "System generated" option for place where you can use a document reference. 

Actually it woudl be prefered everywhere any kind of schema is used to be able to reference it in other parts.

So also support for next schema (containing) options would help and saved time:

  • WSDL
  • API specs 2.0/3.0
  • AVRO (kafka streaming)
  • XSD
  • JSON-schema
  • ...

Kind regards,

Ronald

Idea priority Medium

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.