Data Page throwing ConnectorException propagates FAIL to callers
Data Page load using Connect-SOAP does not handle the external system exception gracefully if there is a SOAP failure.
This application requirement is that checking all the data pages before loading the portal.
Error handling is implemented using a data transform and referring all the data pages.
If there is a failure in one of the data pages load, then it is handled gracefully.
Unfortunately application error handling logic is not triggered if there is a Connect-SOAP failure during data page load.
Soap Service failed exception
Steps to Reproduce
1. Force data page load issue through connect-soap failure.
2. Handle the exception in data pages.
Closer look at the exception indicates that failure is triggered by 'IndeterminateConditionalException' in a 'When' rule, which resulted the reported behavior.
Pega code change is made to handle this exception.
0% found this useful