Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Not under consideration
Created by Guest
Created on Mar 9, 2018

Potential glue tasks Resolution

To resolve Glue Tasks using Inspector when an Entity has multiple Glue Tasks, the tasks must be resolved one-by-one and then the entities can be merged. This means that a job which should take 1 minute requires 5 to 10 minutes of a steward's time.
For example, let's assume you open a Glue member task which has two entities and the entity with the trigger record has a total of 5 Glue tasks. If the steward decides that the entities should be linked, the steward must open each of the non-trigger tasks, resolve the tasks without linking and then return to the glue task, link the members and then resolve the tasks.
It should be noted, that when an entity has multiple glue tasks, in the overwhelming number of cases, all the glue tasks are for the same entity.
The first change we are requesting is: When an entity has multiple glue tasks, the steward should be able to merge the entities and resolve the trigger tasks. The remaining glue member tasks should be re-evaluated to determine if they are still valid. In most cases, they will no longer be required since the entities have been merged. In this case, the tasks should be deleted.
The second change we are requesting would greatly reduce the number of glue tasks created and reduce the workload of the stewards. Currently, glue tasks are created when an auto-link would result in two multiple member entities would be merged. However, often all the members in the first entity strongly match the members in the second entity. In this case a glue task should not be created. A glue task should only be created when a linkage would result in two members which score low would be linked.
To be clear: We would use a second threshold which I will call the Glue Threshold. This threshold would be smaller than the auto-link threshold and probably smaller than the review threshold. Before merging ANY two entities, all members in the first entity are compared to all members in the second entity. If any of the comparisons result in a score lower than the Glue Threshold, a Glue task is created. If none of the comparisons result in a score lower than the Glue Threshold, the entities would be merged.