Thanks for the prompt responses!! ill give that a poke.
--- In vantage@yahoogroups.com, "Charlie Wilson" <foamdesigncsw@...> wrote:
>
> You need to use a choice instead of a condition the condition is stopping
> the whole flow.
>
>
>
> Use the choice and send one outbound on through the rest of your processing
> and one to the finish. When a bad number comes though it will finish the sub
> and bump back to the master flow which will pull the next number.
>
>
>
> ~Charlie
>
> _____
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
> rob.bucek
> Sent: Thursday, March 12, 2009 10:26 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] service connect - condition element
>
>
>
> I am passing records to a subwork flow, synchronously, and cycling execution
> enabled. The first element in the sub is a condition. if the jobnumber is
> blank, null, missing whathave you stop the path of that record. That part
> seems to work fine. However if it does find a record (im using an xls file
> with mulitiple records) with no job number the entire process piles up. For
> example if i have 5 lines in that xls file and line 3 is missing a job
> number line 4 and 5 never get processed. How can i get it to continue on
> with the other records that may be just fine? Thanks in advance!!
>
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.0.237 / Virus Database: 270.11.10/1995 - Release Date: 03/11/09
> 20:42:00
>
>
>
>
> [Non-text portions of this message have been removed]
>