IBM Data and AI RegTech 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:

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 offering manager 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.


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

Shorter URL for this site is: http://ibm.biz/WFS-Ideas or https://ibm.biz/RegTech-Ideas

Inbound Transaction Hierarchy filter issues

Customer is asking to display all transactions for the bundle in case of
the control balancing, this is out of design scope.

We designed that filtering should apply to the transaction level based
on their own attributes. Unfortunately we do not propagate higher
parent's oob amount into the transaction level. So if bundle/segment has
OOB amount 100, such will not be used to filter in the transaction
level.
Same was for the transaction balancing(We only filter the first item
within the transaction using OOB amount field).
OOB amount field is the logical attribute not physical attribute in the
item(or transaction level).

To satisfy the customer's need we have a function to find the next OOB
item.

The way TCR should be used is to access the transmission hierarchy and
find next OOB, then perform an insert or update (The dialog display the
entire transaction in case of the transaction balancing). Balancing is
expected to occur sequentially not going back and forth..

I see the customer wants more than originally implemented but this
request seems more like the design change.
Please request if the customer can use the next oob finder as a work
around. Otherwise, this requires an RFE, not a PMR.
  • Guest
  • Apr 5 2019
  • Delivered
  • Admin
    Craig Rector commented
    23 Oct, 2020 02:26pm

    We now allow you to insert, and then move to credit, which satisfies this requirement we believe.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.