Skip to Main Content
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.


Status Future consideration
Workspace App Connect
Created by Guest
Created on Feb 20, 2015

User-defined node implemented as a subflow must be usable within subflows

Currently a user-defined node "implemented as a subflow" in fact is implemented as a message flow (.msgflow). In consequence this leads to the limitation documented in http://www-01.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bs68460_.htm.
We have implemented multiple subflow UDNs and we cannot use them in subflows.
This limitation must be removed so that the UDNs can also be used in subflows, especially in subflows that are generated by the Integration Toolkit, e.g. when creating an Integration Service.
Furthermore a UDN project within the Integration Toolkit always shows warnings if the project contains UDNs that are implemented as a subflows and these warnings cannot be resolved by an application developer.
The UDNs "Implemented as a subflow" must be implemented as a ".subflow" as indicated by the "Implemented as a subflow" that is shown as an option in the UDN wizard.

Idea priority High
RFE ID 66814
RFE URL
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Reply
    |
    Jan 20, 2021

    RFE Review. Apologies for the length of time this RFE has been in the status of Uncommitted Candidate. This remains a very valid RFE and one we have spoken about internally many times, and one which disproportionately effects our industry pack deliverables which make heavy use of subflow user defined nodes. We continue to monitor this RFE in the hope to apply business prioritization in due course. Status for now remains as Uncommitted Candidate.

  • Guest
    Reply
    |
    Oct 7, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Connectivity and Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

  • Guest
    Reply
    |
    Jun 29, 2015

    Thank you for raising this RFE. We agree this would make an excellent enhancement to the product and would greatly assist with the reuse of User Defined Subflow nodes in more areas of the product. The status of this RFE is updated to Uncommitted Candidate.