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
Medium - Important