Combined with WWF and WSS

Translated to understanding WF in WSS and Office 2007 v1.doc
Author: David Chappell, Chappell & Associates)

See: http://www.davidchappell.com/blog/index.html for full text

As described earlier, the WF runtime engine can host any windows application. In this regard, wssv3 has the most obvious performance. The engine host contains one or more workflow templates. Each workflow template containsCode. It can be installed on the server. In this way, a specific template can be associated with the document library, list, and document type on this server. These workflow templates are loaded and run by the WWS host engine, and then a workflow instance is created. The following figure shows the working principle:

Like all WF workflows, these wssv3-based applications depend on the WF running service. To better support workflow hosting on WSS, wssv3 replaces some built-in services. WF's standard persistence service has been rewritten. For example, you can allow the status of a persistent workflow to connect to the associated documents and list records.
It will be very useful if you have a structural diagram of How to bind it. Architecture diagram is a basic way to understand the workflow in wwwv3 and a best way to understand how the workflow works. However, it looks like a typical scenario of this technology. The next section uses a simple example to explain how to use WSS workflows.