IBM WFSS Ideas Portal

 Welcome!

 

Our team welcomes any feedback and suggestions you have for improving our offerings. This forum allows us to connect your product improvement ideas with IBM product and engineering teams.

 

For product documentation, see Knowledge Center.
Create and View Support Cases and Use the Discussion Forum here

 

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

 

The shorter URL for this site is:   http://ibm.biz/WFS-Ideas

IBMers, please visit the WFSS Internal Ideas portal https://ibm.biz/WFS-Internal-Ideas

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:
- INBOUND_PHYSICAL_TRANMISSION_DATA_V
- INBOUND_PHYSICAL_TRANMISSION_STATES_V
- INBOUND_TRANSMISSION_DATA_V
- INBOUND_BATCH_DATA_V
- PROCESSING_BATCH_DATA_V
- INBOUND_SEGMENT_DATA_V
- TRANSACTION_DATA_V
- TRANSACTION_STATE_V
- OUTBOUND_BATCH_DATA_V
- OUTBOUND_TRANSMISSION_DATA_V

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.
  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Apr 9 2019
  • Capability Already Exists
Component APIs & SDKs
Priority High - Critical
  • Attach files
  • Admin
    Craig Rector commented
    09 May 18:54

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