Hi Amala,
You can check this docops Define the Reset Operator for Exception Handling - CA Process Automation - 4.3 - CA Technologies Documentation
So the effect that you want is should let the exception handler centralize your error-handling. So you should remove all stop operators of your main process, and create 4 exception operators (one for each type of possible exception). You should also name the operators with the same prefix, like Exception_1, Exception_2, Exception_3, Exception_4.
Connect all 4 with an Or operator followed by a Javascript Operator.
If you read the docops link, you know that the when one Exception is trigged, it has a .Source, so the way we do it if a for, looking for a not undefined Source attribute. A generic javascript code for this looks like this.
Process.shouldRetry = false;
for (var i = 1; i <= 4; i++) {
var operatorSource = Process["Exception_" + i].Source;
Process.faltOperator = operatorSource;
if (operatorSource != undefined && Process.retryCount <= Process.maxRetry) {
Process.shouldRetry = true;
Process.retryCount++;
break;
}
}
As custom exits of this javascript operator, you should check if Process.shouldRetry == true, pointing for the retry operator using the Process.faultOperator as a parameter.
And at last, a Process.ShouldRetry != true that should point for the Stop operator.
I don't have access to a ProcessAutomation right now, but later I'll post a simple example of this thing.