IBM RegTech Ideas Portal



Our team welcomes any feedback and suggestions you have for improving our offerings. This forum allows us to connect your product improvement ideas with IBM product and engineering teams.


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


Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases


The shorter URL for this site is:

IBMers, please visit the WFSS Internal Ideas portal


note: The IBM ICM IDEAS Portal is no longer available at this location. If you have reached this page, please look for a new link in the Varicent Administrator. Direct links are found under the "?" in the upper right corner.
A period of transition is likely to impact this service, while ICM becomes Varicent. Please contact Varicent support if you have additional challenges or concerns.

ACK messages handling

Our users manage messages waiting for ACK in MERVA in this way: when a
message is delivered to WBIFN to be sent, itis also recorded in a MERVA
queue called WAITING ACK. This queue is visible to final users.
When the ack arrives, the message is deleted from the waiting ack queue, so only messages which does not receive ack stay in there.
Sometimes our users had to move some of these messages in other queue to be resent, due to problems, and in this way they didn't need to
retype or reauthorize those messages..

We ask to implement the same management in FTM4SS
  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Apr 9 2019
  • Will Not Implement
Component Usability
Priority Medium - Important
  • Attach files