Document type contexts

Document types can be used in different contexts:

•	Archive context

•	Message context

•	Post-processing context

You must specify which metadata to enable and use in each context.

Figure 5

Metadata (MD1, MD2, etc.) enabled in different contexts

Archive context

In Archive context you specify which metadata to store in the Collector archive, and to use in StreamStudio Collector to search for documents in the Collector archive.

In this context, you also have the option to store the following predefined system metadata:

External Job ID	This metadata must be set by the SetExtJobId scripting function. It can be used to identify documents related to specific input jobs.
Receiver	This metadata is set in the runtime output connector settings in Design Center. It can be used to identify documents related to a specific receiver.
Sender	This metadata is set in the runtime job settings in Design Center. It can be used to identify documents related to a specific sender.
Expiring date time	Date and time the document expires, and is ready to be removed from the archive.
Tracker ID	The globally unique identifier (GUID) of the top job.
Application domain ID	Implemented for future use and not used in this release.

Message context

In Message context you specify which metadata to store in Message storages in the runtime repository. This metadata can be used by Correspondence Reviewer and other web services that use the WSDocument API:s.

In this context, you also have the option to store the predefined system metadata External Job ID.

Post-processing context

In Post-processing context you specify which metadata to store in Post-processing storages in the runtime repository. The metadata can be used when post-processing documents (enveloping and sorting).

In this context, you also have the option to store the predefined system metadata External Job ID.