Use a Configurable Auto Start component. In the embedded model, drag out a Day of Week Rule. Hook up all but Tuesday to an End component where the StartWorkflow flag is set to false. Hook up the Tuesday path to an end component where the StartWorkflow flag is set to true.

When deployed, have this workflow be scheduled to be run once daily. It will "fall out" of being run every day except Tuesday.

Hope this helps.

Just make sure you have the "Start until Autostart does not run" UNCHECKED, otherwise it will run every minute when the Check Timeouts and Escalations runs.

Also, if you use a monitoring project, I would not make it a web service. Instead you should make it into a Windows Service. This way it is not dependent on IIS in any way. You can set the schedule to anything you want, and you can also use a named service account if you need to access any shared or network resource.

rob

Thank you guys...

I need to use this resource, i will go any tests,

Thank you again..

Regards

Hey mlowe,

I configured an autostart project the way you did in your example. It ran right on time the first scheduled time. I then changed the schedule and republished and havent gotten it to work since. i've completely deleted the virtual directory and republished it, and changed the app pool, but it still doesnt run. But it will run if I browse to myservice.asmx and select invoke.

Have you or anyone else come across this before?

Make sure to restart the LogicBase 2006 Server Extensions service after doing a schedule change and/or re-publish.

Also, you can change the schedule locally on the server without doing an edit of the project and re-publishing it by using the Task Tray Tool (Programs | Altiris | Workflow Designer | Tools | Task Tray Tool). Right-click on the Task Tray Tool when it is running and choose 'Servers', hover over the server hosting the project and then the project name itself and then select 'Edit Schedule'.