Hello,
I propose implementing an exception-aware mashup event to complement ServiceInvokeCompleted. It could be used for triggering status messages, expressions, validators, etc. In addition to that we need something like Returned Data > Error Details (a simple STRING should be sufficient in most cases), which would allow to recover what has been thrown. See an example screenshot attached.
Existing "Service Notifications" functionality doesn't allow to handle exceptions in scripts intelligently -- it only allows to display static status messages (its "[server-message]" placeholder is of limited use, since server messages always contain text "Error executing service .... Message :: .... - See Script Error Log for more details", so they are not suitable for the end users).
Without such functionality we have to catch all exceptions and format error messages in services. Furthermore, to support any non-trivial error handling logic in mashups one needs to invent custom workarounds like wrapping service return values in INFOTABLEs (imagine handling errors for a service that already returns an INFOTABLE -- it's possible, but complex and cumbersome, since it implies outer infotables, expressions/validators and error-prone bindings).
Regards,
Constantine
