Service Connect Stop on Error

You can check for errors using the response as the input schema in the
conversion tool. Look at the error section. There will be an error number
field that will not be zero if an error occurred. You can then make choices
of how to handle the error. I generally use the get by id or if there is
not get by function that suits my needs then I generate a query and use the
get rows to ensure my data is valid before I process anything.



_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Cathlene Fishman
Sent: Thursday, April 10, 2008 2:31 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Service Connect Stop on Error



Hi there!
When you check for your error, use the Task Monitor Component to stop
it from processing further. You can then Use the Task Monitor in
combination with the workflow to set up a resubmit or deletion
workflow path to assist yourself and/or your user.

Cathlene

--- In vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com,
"laidig.systems" <laidig.systems@...>
wrote:
>
> Does anyone know how to stop my service connect workflow upon an error
> (timeout, invalid schema, business logic conflict)? I have made
> fairly complex workflows and when the first call errors, it doesn't
> stop my workflow, but continues and i have erronios Vantage
> transactions to take care of.
>





[Non-text portions of this message have been removed]
Does anyone know how to stop my service connect workflow upon an error
(timeout, invalid schema, business logic conflict)? I have made
fairly complex workflows and when the first call errors, it doesn't
stop my workflow, but continues and i have erronios Vantage
transactions to take care of.
Hi there!
When you check for your error, use the Task Monitor Component to stop
it from processing further. You can then Use the Task Monitor in
combination with the workflow to set up a resubmit or deletion
workflow path to assist yourself and/or your user.


Cathlene

--- In vantage@yahoogroups.com, "laidig.systems" <laidig.systems@...>
wrote:
>
> Does anyone know how to stop my service connect workflow upon an error
> (timeout, invalid schema, business logic conflict)? I have made
> fairly complex workflows and when the first call errors, it doesn't
> stop my workflow, but continues and i have erronios Vantage
> transactions to take care of.
>