Skip to Main Content
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: or

Status Not under consideration
Component Usability
Created by Guest
Created on Aug 9, 2019

Ability to make auto-populated TCR custom advice attributes uneditable and/or hidden

Why is it useful: Because some of the auto-populated fields for advices do not need to appear in adjustments, this will give us better control of what the operator can see.

Who should benefit from it: Balancing operator

How should it work?  Add flags for the CIF User Exit to inspect and hide and/or make the custom advice attribute fields uneditable.

  • Admin
    Craig Rector
    Sep 15, 2019

    Thank you Mariko. I will reclassify this Idea to "Will not Implement"

  • Guest
    Sep 9, 2019

    9/9/2019 We had a discussion about an internal work around to this enhancement today.  We are going to pursue our internal solution (handle the uneditable fields by the CIF User Exit, remove the fields to be hidden from the DSU workbook and add the required fields to the custom advice XML file to they will be printed on the resulting advice notices), so we will not be needing this enhancement after implementing our internal solution.  Thank you.

    Mariko Arant