Please explain how to use the Catch step in Server Connect. I can't find any reference to it at all on the DMXzone site. I assume it's to catch errors, then to add whatever action to run when the error occurs.

Hello David,
What exactly do you need to achieve?

Hi Teodor,
I am not sure if David shares my assumption: The meaning of some expressions found in the graphical tools are hardly explained. I also wondered about "catch" but also more expressions.

The videos are a great tool but also linear: They explain one explicit "how-to" very well but don't suggest alternative steps, combinations or forks sufficiently to get an idea what else would be possible. A good documentation would lighten the burden for those working at the dmx hotline because we could help ourselves without asking for support. If someone would provide a book or pdf with more examples I would be willing to pay extra for it.

The examples on our website are about a specific usage case of course. We cannot cover hundreds of different usage cases ...
The tutorials idea is to see how it works, then you can just use the products the way you need, changing the things you need and combining what you've learned in different tutorials.
The question is still - what exactly do you need to achieve, so that you ask about the catch step?

I agree. It should be easy to just tell us what the "catch" step is for? I have wondered the same thing. Don't have to cover hundreds of usage cases. Just tell us what it does? And how it works?

thanks

Normally, if you have not defined any steps under catch and some of the steps in your server action results in an error - then the server action just ends, and an error message is generated.

If you want to create your own error handler, like for example - sending an email, when there was an error during executing the server action, you place the send mail step under catch.

Another example - you insert some data into the db and then upload an image related with this record, but the upload returns an error ... you can remove the last inserted record in the catch steps.

That's a great feature,
Thanks for explaining

Thanks Teodor - so I was on the right track

BTW thanks for the Server Connect Conditions video - very useful.

Dave