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 Oct 16, 2024

Rediscovery of a Web service should be possible if the location of the Web service changed (e.g., its URL or file location)

There has been a change at VKB that now requires each service being called through an NGINX reverse proxy. That change implied that the location changed from where WSDLs for Web Services are obtained: BAW should now rediscover all services via the reverse proxy instead of directly from their server.

 VKB needs the rediscover capability for all their services continue working. However, for re-discovery BAW today relies on the location of the WSDL to identify that a service is to be rediscovered, not to be discovered as a new service.

That is, VKB’s expectation is that through rediscovery, the endpoint of the service inside the WSDL file should be rewritten for correctly pointing to the NGINX reverse proxy.

 In case TS016819532, VKB was told that this operation is not considered a rediscovery of the same service, but the discovery of a new one and that this works as designed.  The reason is even if you are referring to the same WSDL file, the server and the endpoints are different.

 However, once you discover a service anew, all the artifacts are re-created. And when there is a conflict in name an “_number” (_1, _2, etc.) is added at the end of the name. Also, a new server definition is added.

 For VKB this is a big problem because a new service name would be needed and all mappings in the process app would need to be re-applied. VKB had already trouble with this in the past. We are talking about nearly 100 WSDLs which will have a different URL.

These changes can have a huge impact on the function of the process applications, and all process applications and their services need to be tested again.

This is why VKB suggests that the change of the endpoint should be considered as a rediscovery of the same service in BAW and not as a new one.

Idea priority Urgent