Chapter 7 Consolidating documents in the repository

Introduction

You can use the consolidation feature to store a document into the repository. When you consolidate a document for the first time in the repository, you must have the Write or Full permission on the target folder or root node. When you update an existing document, you must have the Write or Full permission on this document or on one of its packages if you want to consolidate a PowerDesigner model.

For more information on permissions, see section Defining access permissions on the repository contents in chapter Managing Repository Documents.

When you consolidate a document, you create a document version in the current branch of the repository. A version always belongs to a branch, you always consolidate document versions in the current branch. If you want to consolidate a document into another branch, you first have to change branch.

PowerDesigner checks the uniqueness of document names within a folder or at the root of the browser at consolidation time.

When you are working in a team environment it is important to have rigorous user administration and task assignment to create an efficient work organization.

When you are using PowerDesigner, you can adopt one of the following work organizations:

Freeze any new version in the repository In this case, each time a user consolidates a document, the existing repository version is frozen and a new version of the document is created. This method is very safe but also very space consuming in your database.

Update versions in the repository and freeze some of them Document versions are updatable upon consolidation. The team leader can decide to freeze some versions for archive purpose.

For more information on document versions, see chapter Managing Document Versions in the Repository.