About Instancing
Use an Iterator to perform document instancing before
creating content within the <Body>. The iterator resides directly
before the <Instance> element. The document level iterator contains
business logic and a corresponding PTR. The document level iterator determines how the
rules are written for the entire document.
Each instance signifies a separate document for a transaction. For example, a document may be required for each borrower on the loan.
<Instances>: The container for all of the
instances.
<Instance>: The container for a specific
version of the printed document.
<InstanceFormattingMetadata>: When a new REQ
file is created, the base InstanceFormattingMetadata is blank. The
InstanceFormattingMetadata can be changed if there is a business need. The stylesheet
will apply standard formatting. Elements under InstanceFormattingMetadata only need to
be entered in the .REQ if it needs to override the defaults in the stylesheet. To
override the available elements, right-click the InstanceFormattingMetadata element and
add the needed elements and their values.
<InstanceDocumentRef>: Contains content
referenced from a specific schema (for example: ExpereDoc)
<Document>: The Document element is a
container for content of the document (everything except the instancing and formatting
metadata. Its children typically include <Tagline>,
<Metadata>, <Prolog> and
<Body>.