Integration


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 Nov 1, 2024

RELATED IDEAS

ACE BAR include the option to generate default values (“Build message tree using schema data types”) when validate option is enabled

We have around one thousand ACE v12 flows that consist of SOAP services (SOAP Request + SOAP Reply).

In the flows, we build the SOAP reply message using ESQL, but we are facing an issue regarding the reply message: Some fields with "default value" in XSD are not being generated and this generates errors in our ACE ESQL code.

In order to avoid massive changes in flows code "we will require that ACE BAR includes the option to modify the property “Build message tree using schema data types” that is found in “Input Message Parsing” -> “Parsing Options”, at the same time that the property "Validate" in "Validation" tab is enabled as well. We require this option to be available via the command "mqsiapplybaroverride" and toolkit BAR Editor as well.

This is a sample XSD excerpt:

<xsd:element default="0" minOccurs="1" name "AccountType">
<xsd:annotation>
<xsd:documentation>Account Type</xsd:documentation>
</xsd:annotation>
<xsd:SimpleType>
<xsd:restriction base="xsd:int"/>

In the XSD sample, we want that the type "AccountType" is printed in the resulting message tree with the value "0" when this data is not present in the incoming message.

Idea priority Urgent
  • Admin
    Ben Thompson
    Reply
    |     Dec 4, 2024

    Thank you for taking the time to raise this idea, and also for the link to the service case where deeper discussion has occurred. For the benefit of other readers, the case explains that a default value can be applied on input to a flow, and if the minOccurs is set to 1 and not 0, indicating a mandatory field, then the default value is applied. As requested, it would also be possible to add configuration to the product to enable a default value to be injected on top of the current tree structure in memory at the point of tree serialization on output. In theory we see the benefit of implementing this request for a subset of our userbase (and we note the large number of votes from your in-region IBMers!) yet we also note that the documented behaviour regarding default values on input and output has been this way for many years without escalation from other customers. Status of the request 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.