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 Functionality already exists
Components API & SDKs
Created by Guest
Created on Apr 9, 2019

Have FTM Public Views That Mirror Control Center's UI Data Model

The FTM Control Center's operational data model consists of:
- Inbound Physical Transmission
- Inbound Transmission
- Inbound Batch
- Processing Batch
- Inbound Segments
- Transactions
- Endpoints
- Outbound Batches
- Outbound Transmissions
- Outbound Physical Transmissions

Have FTM PFS public (aka FTMPUB) database views mirror this structure and allow a person to join data across these views. Some example view names are:

The views should be consistent with the following guiding principles:
1) Easily map to the Control Centers user interface data model
2) Have a naming convention consistent with FTM-base
3) Allow for linking of data across the related element (e.g. Batches to the containing Transmissions)
4) Allow for the linking of data objects across the FTM-base and FTM PFS components
5) Balance the need for backwards compatibility and API adoption by deprecating the IPD/check name-based views such as: GW_FILE_STAT_V, INBOUND_FILE_DATA
6) When payment type specific transaction data is required then create payment type specific views such as: CHECK_TRANSACTION_DATA_V and ACH_TRANSACTION_DATA_V.
7) When other payment type specific views are required then create views using a naming pattern of PAYMENT_TYPE_XXXX. Ideally the views are based upon the generic views and appends the additional data/columns.
  • Admin
    Craig Rector
    May 9, 2019

    New views were created as part of v3.2 ,   Please take a look at those to see if they address this specific idea.