Skip to Main Content

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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace Aspera Ideas
Created by Guest
Created on Aug 3, 2022

Add field(s) selector to MongoDB plugin

When using a MongoDB find operation, all qualifying documents are always returned in their entirety. However, there will likely be occasions when only a small subset of the data is actually required in the workflow.

In Mongo Shell, a find operation can include a field filter, like so:
db.testcollection.find( {}, {"scheduling.scheduling-type": 1 })
From matching documents (in this case, all documents in the collection) this returns only the ObjectID and the contents of the scheduling-type field.

Adding the ability to filter to only required fields should improve performance, as less data needs to be sent; e.g. one full document is ~6,700 characters, but getting only one field cut the return size to ~100 characters, cutting down the data sent by more than 98%. This saving, particularly when multiplied out across very large find sets, would reduce network traffic and memory requirements and should improve performance.

Idea priority Medium