Forcing updates into the runtime repository

If you have administrator privileges you can force updates into the runtime repository. This applies to the following types of changes:

•	When the metadata type is changed.

•	When metadata is removed:

–	Metadata deleted (removed from a metadata group).

–	Metadata groups removed from a document type.

–	Metadata group deleted (removed from the resource set).

•	When metadata is disabled in a context.

If you have made any of the changes above, and try to redeploy a Project in Control Center, you receive a message saying you cannot redeploy unless you force the updates into the runtime repository. In this case you have the option to click Cancel and cancel the action, or Force update to force the updates into the runtime repository and deploy the Project. Before you force the updates into the runtime repository you must verify the following:

•	There are no running applications in the application domain.

•	The runtime repository contains no jobs related to affected document types.

•	The runtime repository contains no Messages in Message storages affected by the change.

•	The runtime repository contains no documents in Post-processing storages affected by the change.

•	The runtime repository does not contain any persistent resources related to affected document types.

•	There are no documents waiting to be archived if metadata is disabled in Archive context.

•	The runtime repository contains no saved Collector searches affected by the change.

•	You have a complete backup of the runtime repository.