IBM Sterling Ideas

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

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

Start by posting 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,
1. Post an idea
2. Upvote ideas that matter most to you
3. 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 notifications 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.

Workflow not Halting for Unmanaged Exceptions

Documentation states:

"When no code attribute exists and no match to a defined attribute exists for an onFault element at a level, Sterling B2B Integrator moves to a general onFault (no code attribute) element. If Sterling B2B Integrator does not find a fault code, Sterling B2B Integrator halts the process."

https://www.ibm.com/docs/en/b2b-integrator/6.0.3?topic=oe-when-fault-code-does-not-match-onfault-code

However the last sentence in this is not what currently happens.

in a BP sequence where one or more onFaults (code="xyz") are defined for specific exceptions but there is no General onFault (no code) to handle other unanticipated exceptions, the Error will be logged for the workflow step, but then the engine will not Halt as it is supposed to do, but rather continue processing steps after following the sequence. An Decision with the Advanced Status of -1 is logged in this instance.

Without a background monitoring tool (such as Control Center) with rules to capture errors from these BP(s), there is no visibility that the above error took place and the exceptions can pass unnoticed.


Allowing a process to continue after an unmanaged exception could cause even bigger complications further down the workflow path where output from the activities in the sequence that contained the exception are expected.


Example

Sequence main

Sequence Try This

Activity - A

Activity - B

Activity - C

OnFault code = AnticipatedError1

Sequence Handle AnticipatedError1

OnFault code = AnticipatedError2

Sequence Handle AnticipatedError2

End Sequence - Try This

Activity -D

Activity - E

Activity - F

End Sequence Main


Now say Activity B throws an system exception which we will call "Unanticipated Error"

Activity B will have Error Status

Decision Service "-1"

BP Continues at Activity D....

BP ends state Completed with Error


Expected behavior for an unmanaged/unanticipated error is to Halt at Activity B so that the system operators can see and decide how to handle the exception.



  • Guest
  • Aug 2 2021
  • Future consideration
What is your industry? Other
How will this idea be used?

To correct a workflow issue regarding how exceptions are handled, which currently is different to what is documented.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.