Shape the future of IBM!
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
Shorter URL for this site is: http://ibm.biz/WFS-Ideas or https://ibm.biz/RegTech-Ideas
Due to the pub/sub nature of the interaction from the Distribution Server and the Process Server, the Distribution server publishes messages that are consumed by the process servers so things can go wrong there, that the Distribution Server does not know about. IBM does not have plans to change this design within the next two years.
It does generate a lot of messages, information, warnings, and errors as appropriate. The issue is that, when scanning for the “Distribution Done” message to confirm completion, there’s nothing to note that anything unusual has happened.
A person scanning the results can always rummage through the earlier messages to determine whether it completed successfully, but, to minimize the risk of human error, it should contain something in the completion message to indicate success or failure, not just completion. And for automated scanning, a more "complete" completion message would indicate whether human intervention is needed.
Does the Business Rules Process Server not produce an alert/etc. for the issue it encounters?