Creating Content Versions 

Use

Important processing situations of an original application file that may need to be stored for liability and proof purposes can be saved in secure areas as Content versions You can create one or more content version in a document version for original application files.

This stored version of the original application file was called an audit in previous releases.

Integration

Maintenance of content versions depends on the workstation application. You set the scope of the original model during the definition of the workstation application (Setting in Customizing Document Management ® General Data ® Define workstation application). In order for you to maintain content versions you must set the indicator Content versions supported.

The following additional settings can differentiate the maintenance of content versions:

Processing Content Versions

Activity in Customizing

You must define a status for the document type for automatically creating content versions.

Control data ® Define document type ® Define document status

Set the indicator Create content versions automatically

You must define storage of original application files using the Knowledge Provider (Content Repository) for manually creating content versions.

Control data ® Define document types

Set the indicator Document storage via Knowledge Provider

The storage of content versions can be done in a predefined storage category.
The settings are put together in a profile and allocated to the user.

General data ® Define profile

Enter the storage category

The setting is only read for document types that support storage using the Knowledge Provider.

Features

A content version is only created from an original application file that is not stored in a secure area in its current processing status. Each content version can have one or more Additional files assigned to it.

You can create content version either manually or automatically in Customizing of Document Management.

The secure area where the content versions are to be transported is determined with the following checks:

  1. If the original application file was already stored in a secure area, the system stores it in the same one again.
  2. The system checks if the user has a profile allocated when an original application file is stored in a secure area for the first time. In this case the storage occurs in the given storage category

    3. The setting is only read for document types that support storage using the Knowledge Provider.

  3. If the system could not find storage data a dialog box appears where you can choose from the possible secure areas.

The following graphic displays the original application files that are maintained for a document info record. One content version exists for each original application file. Three content versions were created for the 2D drawing.

Activities

Creating Content Versions Automatically

Creating Content Versions Manually