This could almost work, but I need to know the email addresses of the approvers. That could be accomplished by saving the emails in the metadata, correct?

Yes, that would work. Alternatively, if you have Forms save the submission and instance IDs with the document, WF can pull the field values from Forms. That way, if you change your mind about which form fields you want, you only have to change the workflow definition (and can retroactively go back a re-process existing documents).

This is the approach I would use. Having the submission and instance IDs makes it much easier to go back and pull additional information from Forms when needed, and I use those values to locate documents created by Forms in workflows that are initiated by the same BP instance.

To save the submission and instance IDs, do I create a field that will contain these within the form?

While testing the starting rule, I couldn't get my form to initiate the rule, but other entries were able to. The rule I was using was just "Entry Type == Document", and I had inadvertently run it for every document created within Laserfiche, but nothing ran for my particular form when the PDF was created. I have since limited to just the repository where the PDF is being stored. I can't figure out why the rules didn't run on my entry.

These are built-in variables, so you do not need to add fields on the form itself.

In the Save to Repository task, when you assign metadata to the Form, the instance ID and last Submission ID will be available in the variable list.

Ok. I'm still not sure why my starting rule isn't firing. I've modified the rule to start on Entry Moved to try and manually kick it off myself, but I haven't been successful.

Keep in mind that starting rules become active about 30 seconds after you publish them.

You can check how the event evaluation went in the Subscriber Trace in the Workflow Admin Console.

As far as the rule goes, i think you want it to be triggered by document creation in whatever folder you set Forms to save documents in.

I don't even see my repository listed in the subscriber trace. I'm not the Laserfiche administrator, so I'm not sure how I would add it.

Ok, so it sounds like this Workflow Server is not monitoring your repository. You can add it from the Repositories node in the Workflow Admin Console if you have administrator rights to the Workflow Server. If not, you're going to have to track down your admin to do it.

We were able to add the repository to the monitored repositories in the admin console, but after performing a few Entry Creations and Moves, none of those events show up in the trace log.

Do you see a second tab with the repository name in the Subscriber Trace or just the one tab called "Events"?

Our admin restarted the subscriber service and the new repo tab showed up. I'll continue testing.

After more testing, I can't see any of my Entry Created events in the subscriber log, but I can see them in the Live Event Viewer. If I manually created a document in my repository, my workflow will trigger, but not if I submit/approve in my forms process.

I've been working with our Laserfiche admin, but we haven't been able to determine why these things are occurring/not occurring. 

You do see the events generated by Forms created a document in the Live Event Viewer, right?

What user is Forms using when creating these documents? Are you testing manual document creation as the same user?

The entries that I manually created have a User name field with my domain account, while the Save to Repository task in the Process Diagram saves with the WORKFLOW user.