Chapter 7 Consolidating documents in the repository
The Consolidate Document dialog box lets you select the document to consolidate from the Local Document group box, and the consolidation mode and destination document version from the Repository Document group box.
| Box | Description |
|---|---|
| Workspace
or File |
To select a document displayed (opened or closed) in the current workspace
or To select a file to consolidate. You can browse to select a file |
| Name | To select the name of the document to consolidate. When you click the Properties button, you display the property sheet of the document, if this document is closed in the workspace, it will be opened, this operation can take several minutes for large models |
| Version | PowerDesigner models: if the document exists in the repository, it displays the initial version extracted from the repository, otherwise it displays Unknown.
Other documents: if the document exists in the repository and if you select it from the current workspace, it displays the initial version extracted from the repository. If the document is a file, the Version box displays Unknown. |
| Extract after consolidation | To make sure the local documents reflects the changes performed on the consolidated document after merging it with the repository document (local model is in the left pane and repository model is in the right pane of the merge dialog box), see explanations below |
| Extract dependencies | Lets you extract the generation and external shortcut links for objects in the extracted model |
| Box | Description |
|---|---|
| New | Consolidation mode: allows to create the first version of a new document in the current branch, or the first version of a document into another folder in the current branch |
| Update | Consolidation mode: allows to update an existing version of the document in the current branch or create a new version in the current branch if the document was extracted from a base branch of the current branch |
| Branch | Consolidation mode: allows to create the first version of the document in the current branch |
| Integrate | Consolidation mode: allows to integrate changes in another branch of the version tree of the document, or to consolidate a document under another name |
| Folder | To select the destination folder for consolidation. You can use the Properties tool to display a read-only property sheet of the folder. If you do not select a target folder, the document is consolidated at the root of the browser, you should grant individual access permissions to this document |
| Name | To select the name of the destination document in the repository. You can use the Properties tool to display a read-only property sheet of the document |
| Version | To select a document version |
| Comment | To give a high level overview of the changes brought by consolidation. If you update an existing repository version, the new comment is added to the existing comment of the repository version |
| Freeze before consolidation | To create a new version of modified objects in the consolidated model. The previous version of modified objects in the repository is automatically frozen and a new version is created |
| Freeze after consolidation | To freeze the consolidated document version after consolidation to prevent further updates |
| Create baseline version | To create a new version of the entire model without verifying modified objects. This option does not use the merge feature since a new version is created for any new object (see details below) |
| Unlock after consolidation | To unlock the consolidated document version after consolidation if the version was previously locked. If you do not select this option, the new or updated version is locked whereas the previous version is unlocked |
For more information about the consolidation modes, see section Selecting a consolidation mode
You should select the Create baseline version option when you want to create a new version of the global model without keeping track of individual object versions. The new baseline version provides a picture of the entire model and can be used as starting point for a new development step. This option is restricted to users with Full permission on selected document.
Furthermore, a baseline version makes SQL queries easier since it can be queried without dealing with multiple object versions, as long as the model is not altered by the creation of subsequent versions.
The Create baseline version option does not use the merge interface since a new version is systematically created for each object in the model. This could help you bypass consolidation problems when dealing with objects that are not properly handled in the repository. However, this may be fairly database space consuming.
When you consolidate large models and create a baseline version, the server will create large rollback logs, and use a large number of locks; you might want to configure your server to allow such large transactions.
When you consolidate a PowerDesigner model, and select the Extract after consolidation check box, extraction guarantees the link between the repository and the local model. The next time you consolidate the same document, you will be able to update de repository document.
When you do not select the Extract after consolidation option or when you consolidate an external application file, the link between the repository and the local document is not created. You should save the local workspace to create this link between the repository and the local document and be able to update the repository version.
| Copyright (C) 2005. Sybase Inc. All rights reserved. |
| |