This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
"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."
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.
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 - 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.
What is your industry?
How will this idea be used?
To correct a workflow issue regarding how exceptions are handled, which currently is different to what is documented.
Do not place IBM confidential, company confidential, or personal information into any field.