We have begun creating WCF services for various things which we are creating SmartObjects out of using the WCF Endpoint service. Does anyone have any suggestions for best practices or patterns as to how to do exception handling in your WCF service in this scenario? What types of common things do you catch in your WCF service, and what do you allow to remain unhandled and bubble up to the SmartObject? What do you do to ease the handling of exceptions when you use these custom SmartObjects in workflows or SmartForms?
WCF Endpoint Exception Handling Best Practices
+4
+6Hi,
You could have a look at the following external link from a K2 Partner http://partners.k2.com/en/how-to-k2-aug13.aspx where you should find a link to download a presentation on EndPoint Services (please note that this is not an internal K2 document)
Regards,
+3Always try to handle anticipated exceptions. For example if an input parameter in the service method falls out of range or is an invalid data type.
A common challenge with web services are execution timeouts. The response may take a while to return and may exceed the timeout limit. Although you can control the limit in the web service by increasing the timeout I still can't find a way of doing this in the service object/broker. What happens is that the request is still processing but K2 eventually gives up if the request takes too long and then raises an exception.
One nice feature in the latest version of smartforms (1.0.6) is that you are able to manage errors with the introduction of the error event in the Rule Designer. This lets you configure what happens when an error occurs.
+3Hello All,
Did anyone got the solution for the same .
Please revert back as soon as possbile .
Thanks In Advance,
Ruchi Agarwak
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.