REST Connector Error Hander Flow ConnectionProblem
Hi All,
I would like to customise the Connector Error Hander Flow "ConnectionProblem", I overwrite it with the same name in a project RuleSet, but when I test it throw a Integrator shape , It seems invoking Pega ConnectionProblem instaed of the custimize one.
Can any one tell me what is wrong please.
Regards
Updated: 9 Apr 2024 8:03 EDT
Maantic Technologies Pvt Ltd.
IN
Hi @ahmedd13,
If you are calling the Connect SOAP rule from Int layer then please save as the customized ConnectionProblem flow in that layer or you can do vice versa.
Maantic Technologies Pvt Ltd.
IN
Can you confirm if your connector class and your customized ConnectionProblem flow is in the same class or is accessible via inheritance?
You can rename the flow as well. The only thing you need to do is specify the error handler flow flow in the "Service" tab "Error handling" section. Make sure your customized rule is accessible from here.
Pegasystems Inc.
CA
I wouldn't recommend customizing the ConnectionFlowProblem in your implementation layer. This could impact your upgrades because new changes made in the platform will not be in effect.
Please check the ruleset stack and ensure the rule is saved into the correct ruleset. Also, please ensure no private edits in your operator for the Connection Problem.
If the problem persist, then please share the screenshot of the rule saved in your implementation layer
LCL
FR
My Custom ConnectionProblem Flow is under work- and in entreprise layer branch RS
We need that all application can use it as a fralework flow to handle integration error.
Pls see the screeshot attached.
Updated: 10 Apr 2024 16:41 EDT
Pegasystems Inc.
CA
I noticed the Flow name is saved as "Custom". You have to save as with the same name to override the OOTB rule unless you are using extension point to configure the custom flow name.
After saving the same name as OOTB, Can you please confirm that you're trying to test with your operator or any other operator who has access to the branch rule version?
LCL
FR
I discover that ConenctionProblem is not handled but FlowProblems is handled in place.
Even I simulate error conenction to the Remote invoked Rest service , a flow error is raised due to a java.lang.NullPointerException which invoke FlowProblems Flow.
Please see joingned the config of the Rest Connector ErrorHandling and also the trace when it's invoked.
