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,
Post an idea
Upvote ideas that matter most to you
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
Christophe, the button currently doesnt serve any function, so you either hide it, which is an indication for the user that they need to use the action button at the top (guidance text can remain) or if hiding the button in the guidance generates complications system wise, make it an actional button. What is the purpose of having a drop down in the guidance if it doesnt trigger anything and they will have to use the action button at the top?
Interresting to see that this function is being used. Thanks for briging this to our attention
To make sure we got this right, we should hide the button
if there is no validation for an action
Other considerations
When hidding a button, we tend to break end user expectations, "why dont I have the button here/now"
should we rather show indicate that no validation defined for the task
the button allows to check for different actions (Approve / Reject action for example), should we only show the one that have validation
Should we validate all potatiial action after each save (this might have an impact)
Thank you for submitting this RFE!
The IBM team is evaluating this RFE. A decision or request for more information will be provided within 90 days of the date that this issue was submitted.