IBM Sterling Ideas
formerly Watson Supply Chain
Submit new product ideas for Watson Supply Chain solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed. Order Management, Store Engagement, Watson Order Optimizer, Inventory Visibility, CPQ and Call Center are now part of Watson Supply Chain
Connect with IBM experts and your peers on the
Supply Chain Collaboration Community and the Order Management Interest Group
Submit ideas for other Watson Customer Engagement Products:
• Watson Marketing
• Watson Campaign Automation
• Watson Commerce
We have to import multiple xsd with nested schemas, so far we have no problem.
The problem is related to the length of some elements, elements that have over then 35 characters
<xsd:element name="senderSoftwareDocumentSignatureHash" type="signatureHashSubsetType" minOccurs="0">
<xsd:element name="senderSoftwareCertificationNumber" type="xsd:string" minOccurs="0">
We can't ask to the provider to change the lenght of both of elements because they are used by othe client's (like us) and the owner of the xsd's is Portuguese Government.
Is that possible to allow/change the name of the fields/elements with more than 30 characters?
We'll wait for good news
How will this idea be used?
WDI scalability for new development requirements
|What is your industry?||Travel & Transportation|
|What is the idea priority?||Urgent|
|Link to original RFE|