I'd envision a resource type similar to a dynamic image that would instead have the ability to dynamically load another PP7 form. Or maybe it would be better as a special pagetype instead of resource type. Essentially, it would call in the "dynamic" form and execute it using the calling form's data.

This would be very useful in dynamically building a document from many different PP7 forms (think insurance policies with 100's of forms and endorsements). Right now this can be accomplished by using Watch to create PDF's out each form and then combine them all into one PDF as the end step. By doing this, though, page level paper settings and finishing are lost.

-nth-

That's a very interesting suggestion. Right now, this can also be achieved by building a humongous single form that contains all possible pages, but that means implementing tons of conditions, variables, and so on. Not to mention it becomes difficult to work in the design tool when so many objects are present.

My main concern with calling external forms would be performance (both speed and size). Each form contains its own prolog and resources that get cached at the start of the form, but if you call multiple forms (conceivably, some would appear more than once in a single data stream), then you lose that cache and the entire job could become huge and slow.

Perhaps by creating some kind of "shared sub-form" template, we could bypass this issue. That remains to be seen.

I'll certainly keep this suggestion on file. Thanks for your comments and keep them coming!

Safeguards would have to be put in to prevent a document calling itself, or a called document from calling the caller, etc.

... I think I've found every possible way to send my Watch server into the Slow Spiral of Death, but this opens new Vistas of (self induced) disaster before me...