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 a Create queue allows to submit an FIN output message as valid message, which leads to massive errors in the processing flow afterwards as you cannot send a incoming message to SWIFT (see ref. PMR).
Therefore creation/editing of incoming messages should only be allowed "on request", if a proper processing work flow is implemented for messages submitted from such a queue (i.e. to create incoming messages to be sent to an application for test purposes).
Having this setting connected to a queue the privilege to create incoming messages can be assigned to dedicated persons with access to such a queue only.
Do not place IBM confidential, company confidential, or personal information into any field.