|
Rank: Member
Groups: Member
Joined: 10/28/2009
Posts: 11
Points: 33
Location: New York, NY
|
I wonder if anyone's got around to building a workflow that can be instantiated as a service.
Aside from the obvious issue that there's no console output, are there any practical hurdles to overcome?
My specific application is pretty simple - I want a service that watches a SAN folder for new files, which are then validated in turn against a combination of xsd files and xqueries, so that the system can figure out how to process and route the files.
Maybe (hint) as new feature suggestion, you build a 'create and deploy as a service' wizard in the interface.
|
|
Rank: Administration
Groups: Administration, Member
Joined: 4/21/2009
Posts: 40
Points: 120
|
Deploy to the agent. If you grab a new serial number and add it to your install (http://blog.powerwf.com/post/217208218/how-to-change-powerwf-license-key) your Deploy to Agent button will be enabled. The PowerWF Workflow Scheduler runs as a service so any workflows deployed to it will be run in that context.
|
