Monitoring or Decision only Workflow?
Created: 08 Juni 2012 | Aktualisiert: 10 Juni 2012 | 4 Kommentare
Dieses Problem wurde gelöst. Siehe Lösung.
I have a WF process that I more or less need to run on a schedule. I built the WF in a "Decision only" model and its ready to go. Issue is how to trigger it. I was looking at my options, and saw the monitoring model type and thought it may be a fit. Question is, how is it triggered?
Kategorien für Diskussion:
Kommentare Kommentare • Zum neuesten Kommentar
Monitoring project types have a schedule built into the Project Properties that you can specify.
You don't have to rebuild the wheel with your monitoring project. You can basically open a brand new monitoring project, then on the pallette of your decision project, do a Select All (Ctrl-A) and Copy (Ctrl-C). Then paste (Ctrl-V) into your new monitoring project. If you had any external libraries you added to the decision project, you have to add them to the monitoring project before you do this.
Then just specify a schedule in Project properties and you're off (top tree node in the tree view - Publishing tab - under Schedule)
The workflow engine is basically responsible for triggering monitoring projects once they're deployed, acc. to the schedule specified.
I believe I found where to schedule the project, but it didn't kick in last night. I didn't use the "Auto Initialize" check box, is that required?
I found in checking some things on the production WF server that apparently I didn't include a DLL... but it still worked on my dev server. Strange. Still, I re-published it and was able to envoke the WF and it worked.
Still I have the question of do I need the "Auto Initialize" check box?
Auo-initialize, I believe, just preloads the flow into memory. I always have it checked, but I don't think it's required.
Möchten Sie antworten?
Einloggen oder registrieren, um Ihren Kommentar zu veröffentlichen.