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
Requirement to resend timed-out transactions in bulks
To cover the requirement to resend timed-out transactions in bulks (selecting multiple alert objects from the FTM UI and resolve them at once) we see two different options:
(1) Override the Outbound Transaction FSM, in particular the E_Heartbeat transition that connects S_WaitingForAck to S_WaitingForAckTimeout. The overridden transition will have a different target state that will contain the “Resend” resolution constraint, along with the “Cancel” option. On the E_OperatorResent event, we will be able to trigger the outbound PT resend. In this scenario the new target state will need the same outbound transitions as S_WaitingForAckTimeout state in order to handle the E_AckRecvd, E_OutTxnAckRecvd and E_OperatorCancel events.
(2) Add a new “Resend” resolution action to the existing S_WaitingForAckTimeout state and add a new transition from S_WaitingForAckTimeout to S_WaitingForAck to trigger the resending process. Of course this means changing the generic FSM, so we should raise the question whether the change is acceptable and can be included in future releases.
Do not place IBM confidential, company confidential, or personal information into any field.