1. In step "Define document types", you can now determine that a document that is released for the first time with reference to a change number is automatically assigned a revision level.

2. In step "Define document status", the following new settings are now possible:

a) Completion confirmation for engineering change management

When you set this status, a document with this status is "complete" in terms of engineering change management. The indicator is only relevant for engineering change management if you edit the document with reference to a change number which is assigned to a change type. In this case, the change functions are controlled via various statuses.

If you want to assign a status for which this indicator is set, the system checks the object management record of the document in the allocated change master.

The document can only receive this status if its current system status has "Release change" as subsequent system status. In this case, the object management record is automatically changed in the change master, and the system status is set to "Release change".
Otherwise, the document info record can contain no status for which this indicator is set.

b) Carry out the audit function

If you set the Audit indicator, original files that are stored in either the archive or the vault are automatically saved in the defined path once they reach this processing status. You enter the vault path in the step "Define data carrier".
Processing statuses that are saved to the vault using the audit function are marked in the status log. You can display them with a double click.

c) Carry out workflow tasks

In the Workflow Workbench, you can define workflow tasks that are triggered by certain events. Then you assign each workflow task to a particular status. As soon as this status is set for the document of the chosen document type, the system carries out the workflow task (for example, display document).

You identify the workflow task in the fields Object type and Object ID.

d) Program exit when a certain status is set

You can determine that an external program is to be run when a certain status is set.
To do this, in the Program exit field, enter the program from which a FORM routine is to be executed.
In the FORM routine field, enter the subroutine that is to be carried out.

The program is run as soon as this status is set and the document info record is saved.

3. Define revision levels for documents

With this function, you define the revision levels for documents. You also define the sequence in which the system is to assign the revision levels.

1. Define data carrier type

As of this release, you can save original application data for a document info record to a vault. The vault is a server which cannot be reached via the file system of the frontend computer. You can define this new data carrier type with the new Data carrier is a vault indicator.
You define the vault path in the step "Define data carrier".

2. The "Data carriers/network nodes" step has been replaced by two separate steps: define data carrier for original application data and define frontend computers in the network.

a) Define data carrier

In this step, you define the data carriers which fulfil the following functions for original application files: printer, archive, vault, server.

Original application data for a document info record is stored in the vault if you select a vault as data carrier or if the audit function is executed automatically.
The vault cannot directly be accessed via the file system. You define the path for storing the original application files in the field Vault path . When you are processing the document info record, for security reasons you only see the data carrier and the short description.

b) Identify frontend computer

In this step, you identify the frontend computers in the network. This includes all work centers from which you want to process original application files, for example, a UNIX workstation (processing a CAD drawing) or a PC with Windows NT (word processing).

All data carriers must be allocated to a data carrier type. The system requires the network address for transferring original application data to every work center.

3. Define mount points/logical disk drives

When you enter original application data using the file manager, you see the prefix of the path for accessing the data as a default path.

4. Workstation application

The following fields for defining workstation applications are new:

a) Interface

With this indicator, you determine that the application can be used with an SAP/CAD dialog interface.
The CAD interface, for example, lists applications that are marked with this indicator for CAD program selection.

b) File suffix for application

If you want to process original application data which is already stored in a vault, SAP database or archive, the system creates a file with a copy of the stored data.
In this field, you enter the file suffix for the file.

c) File format

In this field, you enter the file formats which are relevant to original application data. These are listed for file selection via the file manager.