$eb.executeFunction('fn'); versus Form onError Event

[Steve James]

We had a situation earlier today where we accidentally rolled a change to a form but missed a client script.

The form runs $eb.executeFunction('fn'); but the function wasn't available for the form.

If the form doesn't have a form onError then the function call returns (or can be displayed in the failureCallBack)

Browser developer tools
{"error":{"message":"Server Error: fn is not accessible."},"success":false}

Also the logs show
16-Mar-03 13:43:59:305 | ERROR | Server Error: fn is not accessible.
com.ebasetech.ufs.kernel.FormException: fn is not accessible.


This form had an onError event which fired but the result in the browser was
{"success":true}

the logs showed

16-Mar-03 13:46:15:222 | INFO | Transaction rolled back
16-Mar-03 13:46:15:222 | INFO | Transaction rolled back

I appreciate it is an odd set of circumstances but it was mildly tricky to trace through.

1 - how can I pick up the error in a server side script?
2 - shouldn't the browser result be still show the fail message?

Thanks
Steve

[Jon]

I think this is probably a bug. Failures in a client API call shouldn't invoke the on error event, they should be fed back to the client.