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
MER - attribute to allow/not allow to create FIN Output messages in create queues
We need an attribute for MER queue settings (CT DnqERQueue) to allow or not allow the creation or editing of incoming messages (i.e. FIN Output) in unformatted view. Like i.e. attributes AllowDrafts, CHANGELOCALADDR.Background: Unformatted view in...
SAG Add-on Adding All SAG Certificates to dnfsaomp during Deploy
The SAG Add-on adds all SAG certificates to message partner dnfsaomp during deploy to a SAG. This is an issue for us as we have offloaded the creation of Virtual SWIFTNet Users and SWIFTNet Certificates for SWIFTNet Browse users to our Security ...
Currently, FTM for SWIFT Service does not formally support Db2 pureScale as FTM database on AIX platform, and has not been tested with it. Without pureScale support by FTM SS, it would not be able to provide Active/Active configuration for FTM dat...
Introduce message length check in MER, analogue to the length check performed in DNF_ILC_FIN.
Introduce message length check in MER, analogue to the length check performed in DNF_ILC_FIN.The business impact: A message which is successfully validated in MER may nevertheless fail to be send to SWIFT, because it fails the length check in DNF_...
In MER add the possibility to search / filter the templates, saved in a queue, by field: "Description"
The user should be able to search the messages in a MER queue, by applying a filter on the column: description. This is useful if a user created a lot of templates and he inserted a particular description for every one.
We use our companies internalcryptic IDs (ie nj123456) to add a user to FTM MER. FTM MER should provide a field to also add the uers full name (ie David Jones). Our audit department is requesting this.
List Current Active users in MER, RMA & AO Facilities
Request for a function to list/display active users (currently logged on FTM users) in the FTM AO Facility . Display the currently active (currently signed in into FTM.Additional Details: Merva can use function DU (Display Users): AC00 MERVA ESA...
The Data Entry(Create Purpose) queue information is not reflected in Message History and the user who performed the AU2 function is not displayed in Message History.
The Data Entry(Create Purpose) queue information is not reflected in Message History and the user who performed the AU2 function is not displayed in Message History.In the attached image, a message is created in the TCPDE queue, but queue informat...
MER and RMA screens displaying incorrect datetime in browser
PBB required a short term solution to to display correct datetime in Browser (MER and RMA screens). It would be great if there's a configurable option to control the display of timestamp in browser:* default - the current behavior, displaying loca...
Do not place IBM confidential, company confidential, or personal information into any field.