Multiple Valid Document Versions

Initial Situation:

In a configuration several object type versions are created (identical change number, data package and object relevance). Also a relation is defined, setting the document status (action).

Without further configuration, the status of all versions will be the target status (if possible).

If a selection is required, e.g. the user shall be able to select the document version to be used, the procedure as described below must be followed, respectively the described conditions must be fulfilled.

• Triggering relation of action (action 1) must set the document status and can be triggered by a configuration type or a document.

• Several active versions of the identical document object must be available as target object (identical object type, change number, data package and object relevance).

• A second relation of action must be defined (document  document, action 2) which requires:

  • Key object type 1 must fully comply key object type 2 of action 1.

  • Key object rel 1 must fully comply key object rel 2 of action 1.

  • Key document status 1 must fully comply key document status 2 of action 1.

  • Key object type 2 must fully comply key object type 2 of action 1.

  • Key object rel 2 must fully comply key object rel 2 of action 1.

Only if all conditions are fulfilled, the user can select the target status of this action when processing action 1. Action 1 will then trigger action 2. Example: as action 1 triggers a release, action 2 could set a Stop status and mark all versions which should not be used.

If action 2 shall only trigger the selection dialog but without setting any status, the document status 2 of action 2 can be set identical to document status 1 of action 1. As all versions, which are not selected already have this status, action 2 will not carry out anything.

Remark:

Document versions, which have not been selected by action 2 will be ignored in case of checks on the document type and object relevance as long as they are keeping their status defined by this action. If further status changes are performed later and these versions shall be ignored, customer exits are required. These document versions will then also be ignored for further versions and derivations.