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
In our current IMR solution, it is using OP as the front-end to call the back-end BPM process to support the workflow.
Inside the BPM process, there is a key task for BPM to use OP Rest API to connect to OP and perform data updates in the object(s), and this is the most frequent failure point during the BPM process execution. By looking at what BPM got as a return of the API, it is a very generic error code (HTTP Error Code 400 or 500) that we would not be able to know what causing the failure and what the possible handling required for the failure.
To my understanding, OP should provide a proper response code to inform the caller what the issue with the failure call, regardless who are the callers (BPM or other system). The generic error is not meaningful at all to the caller, and this is where the concern from and seeking IBM's support for a solution.
Do not place IBM confidential, company confidential, or personal information into any field.