Re: Workflow - skip multiple tasks?
From: Peter A. Schott (pschott_at_no.spamm.hear.drivefinancial.com)
Date: 09/21/04
- Next message: Peter A. Schott: "Re: Workflow - skip multiple tasks?"
- Previous message: Mark Kurten: "Re: transferring data via odbc"
- In reply to: Allan Mitchell: "Re: Workflow - skip multiple tasks?"
- Next in thread: Allan Mitchell: "Re: Workflow - skip multiple tasks?"
- Reply: Allan Mitchell: "Re: Workflow - skip multiple tasks?"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 21 Sep 2004 16:10:20 -0500
I think that was my confusion. Problem was looking at the sample package for
multiple paths - with everything being ActiveX, I wasn't sure if I needed to
have a new step in between to split and another step to re-merge the paths. I
will see if I can put a "success" constraint straight out to my Log, Move file
steps from my first step.
I'll go back through the sample again. I'm not quite getting the part about
disabling the "On Success" workflow for one and not the other.
Thanks.
-Pete
(C'mon Yukon!!!)
Allan Mitchell <allan@no-spam.sqldts.com> wrote:
> In article <mhduk0521lvt8dnmhvdifvgh5tdlsh60fa@4ax.com>, Peter A. Schott wrote:
> > I've reviewed a couple of the posts @ sqldts.com and was wondering if it's
> > possible to skip multiple tasks and jump directly to the end.
> >
> > I have something like this:
> >
> > Check for files
> > Check size here for data in the file. If no data, skip to Logging step
> > |
> > V
> > Import data & Other misc processing in 4-5 steps
> > |
> > V
> > ExecSQL task to put filename, size, and current datetime in a log table
> > |
> > V
> > Move file to a "Processed" directory in case of future issues.
> >
> > I always want the ExecSQL and Move steps to run if a file exists. I've
> > already got some logic in place to handle "no (more) files" by directing to a
> > Finished step. However, when I try to implement this, I get no steps running.
> >
> > I can't disable the first import step or I get no further steps running.
> > I can't enable the first import and set my Log step to waiting because it then
> > flows through the Import path.
> >
> > I'm hoping to do this without the "switched" paths that I've seen. However,
> > if I have to create a simple ActiveX script that will just return success, I
> > guess I can do that. Not sure if that will route correctly to an ExecSQL task
> > or if I'll need another ActiveX task to pick up right before that.
> >
> > Any ideas? Is there an easier way to do this short of going to Yukon? (SO
> > wish we could use that - would make most of this task easier....)
> >
> > Thanks for all of your help.
> >
> > -Pete Schott
> >
>
> OK so you have a line of tasks. If the file meets the criteria then you want to
> run through them all else you want to skip to the last step
>
> If I am right then at the start of the line of items you put in an active Script
> task that asks the file if it meets the criteria. It has an on success
> constraint to the line of tasks that do the importing.
> You also add an On Success Constraiint from our starting Active Script task to
> the last task which you always want to run.
> ( The last task should have 2 On Success Constraints entering it)
>
> You can then enable or disable the step that does the importing depending on if
> the file meets the criteria. The two constraints entering the last task mean
> that both these conditions must be true so if you do the import then fine but if
> you decide to skip you will need to use this article to fake the result.
>
> Multiple Paths in Workflow
> (http://www.sqldts.com/default.aspx?218)
- Next message: Peter A. Schott: "Re: Workflow - skip multiple tasks?"
- Previous message: Mark Kurten: "Re: transferring data via odbc"
- In reply to: Allan Mitchell: "Re: Workflow - skip multiple tasks?"
- Next in thread: Allan Mitchell: "Re: Workflow - skip multiple tasks?"
- Reply: Allan Mitchell: "Re: Workflow - skip multiple tasks?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
