Hi Dave,
In case it helps, here’s an example.
I created an action to create database records for contents of an image folder. The process appeared to work fine but in fact stopped before all the records were created. It turned out one of the files had a size of zero bytes which stopped any more processing. This was an unexpected and rather unlikely problem, probably caused by an FTP error (the files mighit be uploaded via a browser or FTP).
I added a response step like this:
In App Connect, I added a dynamic event to the server action - using the ‘Invalid’ option. You can then include these bindings in a notification for example:
… which, in this case, will return:
400
Bad Request
imagename.jpg
I’m sure there’s a lot more potential with this feature than I’ve used or discovered so far. Eg I would be interested in knowing more about specifying the status in server connect and the triggering of dynamic events in app connect.