Skip to Main Content
Digital Business Automation Ideas


This is an IBM Automation portal for Digital Business Automation 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.


Please use the following category to raise ideas for these offerings for all environments (traditional on premises, containers, on cloud):
  • Cloud Pak for Business Automation - including Business Automation Studio and App Designer, Business Automation Insights

  • Business Automation Workflow (BAW) - including BAW, Business Process Manager, Workstream Services, Business Performance Center, Advanced Case Management

  • Content Services - FileNet Content Manager

  • Content Services - Content Manager OnDemand

  • Content Services - Daeja Virtual Viewer

  • Content Services - Navigator

  • Content Services - Content Collector for Email, Sharepoint, Files

  • Content Services - Content Collector for SAP

  • Content Services - Enterprise Records

  • Content Services - Content Manager (CM8)

  • Datacap

  • Automation Document Processing

  • Automation Decision Services (ADS)

  • Operational Decision Manager

  • Robotic Process Automation

  • Robotic Process Automation with Automation Anywhere

  • Blueworks Live

  • Business Automation Manager Open Edition

  • IBM Process Mining


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.


Status Future consideration
Created by Guest
Created on Apr 24, 2020

AbstractXMLSe W could not find a known type for

Warning message:
AbstractXMLSe W could not find a known type for

Explanation:
The current discovered WSDL does not fit the response from server. The logged messages happen if the response from server contain BOs, which are not part of the matching WSDL.
It might be that the original WSDL was discovered longer time ago whereas the underlying service changed and returns, from BAW point of view, undefined / unknown BOs. In this case, the given message is being wrote in the log because BAW cannot decide what to do with these BOs and if this is some sort of error or not. Therefor message is from type "warning".
This circumstance can be verified be checking the WSDL, the within BAW defined BOs (for this the app / twx file is needed) and the response from the service.

Expected:
It is expected as a part of the warning that the message contains from which app, module, or wsdl the warning is being created.

Idea priority Medium
RFE ID 141936
RFE URL
RFE Product IBM Business Process Manager
  • Guest
    Reply
    |
    Apr 25, 2020

    This has been a know issue since BPM v8.5.7 and I believe IBM lab is involved in it in the coming releases. This happens when the according field was part of a list type, and the SOAP response for this field is empty.
    --> This behavior can be stopped in two ways:
    1. By setting the property 'serializer-exclude-incomplete-element' to 'true', for instance via 100Custom.xml (Though this has certain limitations)
    2. Set the logging level to *=info: com.lombardisoftware.core.xml.AbstractXMLSerializer=severe and it won't bother you in the logs.