Enabling the Message context for a metadata

A metadata that you define in Design Center is not automatically available to the web applications. To make a metadata available, for example as a document detail in Correspondence Reviewer, you must enable the Message context for the metadata. You must also enable the Message context for any metadata to be used in exception rules.

You configure metadata contexts in the Document Type Editor.

If you disable the Message context in a Project that is deployed, the database column for the context remains in the Message storage in the runtime repository, but is no longer considered by the StreamServer application. Since the database column is still available to the web application, it is recommended to drop the Message storage to avoid any conflicts. For example, by using StreamServe Database Administration Tool. End of warning.

Exception

Metadata used in editable or available texts in Ad Hoc Correspondence does not require the Message context. In the Ad Hoc application, the end-user can edit text strings containing metadata values, but cannot change the actual metadata values in the Message storage.

Prerequisites

The metadata is added to a document type in a resource set connected to the Runtime configuration and is assigned a value.

Note:

To save space in the repositories and improve search performance, you should not add more metadata than required, and you should not use the Message context unless the metadata really needs to be available.

To make metadata available

1	In Design Center, open a resource set connected to the Runtime configuration.

2	Double-click the document type. The Document Type Editor opens.

3	From the drop-down list, select the Message context.

4	In the Metadata groups list, select the metadata group.

5	In the Value assignments list, select the metadata to be made available.

6	Select File > Save to save the document type.

Related topics

•	Document type contexts in the Document types and metadata documentation