8.4

the "Content Status"filter and setting it "Equal to" those states. Two conditions are necessary, and the
"Condition is true when"is set to "all items are met".
l With this list of documents in the metadata, we Branch off. This is done because we need to build a
report that will be sent to an administrator, and only one email should be sent.
l To build the report, inside of the branch we use the Metadata Sequencer to create one sequence
for each document, by splitting at the Document level, by 1 occurrence of the level for each
sequence.
l The Capture Condition task then
Capture Web Manager Workflow
This example is both a more involved workflow for Capture, and an interesting implementation of an
HTTPWorkflow. Before looking at this example, it would be best to become familiar with both "PlanetPress
Capture Workflow" on page 104 and "HTTP Server Workflow" on the next page.
The example is too complex to display as images in this guide, so it is rather available for download. It infers
two different files:
l Capture Web Manager Workflow Configuration (PW7)
l Capture Web Manager PReS Connect Document (PP7)
Technical
This example is compatible with PReS Workflow 7.4 and higher and will not work in older versions.
Installation
1. Download both resource files
2. Create a folder on your disk called c:\PReS
3. Open the invoice.pp7 document and send it towards your local PReS Workflow server (localhost or
127.0.0.1)
4. Open the configuration file CaptureExampleProcess.pw7
5.
Click the PReS Workflow button (File menu) and go in Preferences.
6. In the HTTP Server Input 2 section, check the Serve HTTP resources option, change the Resource
action name box to static , and the Resource folder to c:\PReS\http . Then, click OK.
7. Send the configuration to your local PReS Workflow server.
8. Start PReS Workflow services (see "Start and Stop PReS Workflow Service" on page 479).