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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Idea / RFE Review. Apologies for the length of time this RFE has been held in Uncommitted Candidate / Future Consideration status. Unfortunately business prioritization has not yet led us to implement this requirement, but we still see value in the idea (in fact, the original architecture of the collector node discussed this potential aspect of future enhancement). For now the status is maintained as Uncommitted Candidate but we will continue to keep this on our radar for a future release.
Thanks for raising this RFE, which is a good suggestion for the enhancement of the Collector node. Jan Fluitsma's comment about the aggregation node is also insightful - Aggregations can be grown dynamically, depending on settings made to the Environment tree directly, or based upon the number of instances of the AggregateRequest node used in the flow. That said, using a Collector node to fan-in input messages in isolation of a fan-out process, and to then also allow the collection size which is anticipated for completion of the collection to increase. Status of the RFE is updated to Uncommitted Candidate.
Can't you use the Aggregate nodes?