Jerry has a requirement to fill in scores of PDF forms. The Synapse way of doing PDFs would be too time consuming for him. This is a possible workflow, which requires Adobe LiveCycle designer or similar: Locate User Bring up an applet that displays all the forms in the system ( residing on a mapped network drive ) Click on the required form A templated XFDF file associated with that form is downloaded to the client The client then runs acrobat on the XFDF and fills in some default values User fills in rest User submits the form to Cheyenne ( Physcian web portal version ) A script pulls out the identifying number that links this submission to the patient and stores the results. The identifying number should be unique? so that it can't be submitted again? The identifying number allows us also to know which form this is. That way we only ever need a single server side script to process any type of form. Later on you can view all filled forms for that patient ... ie download the submitted data as an XFDF and recreate the filled in form The task for the user is to add two new fields on every PDF that they want to use viz, a "Submit" button that points to the physician web portal, and a unique form id, which will be hidden. Additionally the user has to generate the skeleton XFDF from the PDF, and place various template variables which they want Synapse to fill in. They have to upload the XFDF with a form description, and a link to where the form is.