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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Add toolkit validation to soap and mapping flows to reduce runtime errors.
When working with SOAP request nodes (with associated wsdl) and corresponding SOAP response nodes and mapping nodes in the toolkit, I wired them together incorrectly and got runtime errors.
When I eventually got to the bottom of the errors; I felt that the tooling had enough information in the nodes and wsdl metadata and the mapping node to identify many of my errors at development time. For example: 1) if a node output is an a particular domain and the subsequent node cannot handle that domain then the tooling should show that and hint as to how to quick fix it. 2) we found we needed to do a SOAP extract after every SOAP request. The flow should have been flagged as invalid if the required extract node was not there or incorrectly configured.
I feel that it should have been possible to validate the flows at development time rather than getting errors at runtime.
I suggest having different levels of this validation, ranging from only validate at deploy time, through to validating every flow save.
My understanding is that this requirement will also cover type propagation, where wsdl metadata and mapping information can be used to identify invalid flows.
Do not place IBM confidential, company confidential, or personal information into any field.