Check in Parameters

Local Document

The Local Document group box contains the following parameters:

Parameter	Description
Workspace or File	[models and files only] Select one of these radio buttons to specify and view the document name by its workspace name or file name and path.
Name	Specifies the name of the document to check in. [models and files only] Depending on whether you have selected Workspace or File, this will be a: Model name - click the Properties tool to the right of the field to open its property sheet File name and path - click the Browse tool to the right to open a file selection dialog.
Version	[not for project – read-only] Specifies the current version of the model or file in the repository, if known.
Check out after check in	[models and resources only] Specifies that the local version will be updated to ensure that it reflects any changes in the repository version after the check in. This allows you to work with the most up-to-date version of a model or resource (contained in a project or not) or where several users may be editing objects concurrently. See Using the Check In Model window.
Check out dependencies	[models only] Checks out any models on which the model (contained in a project or not) is dependent (through generation links or shortcuts) after check in.

Repository Document

The Repository Document group box contains the following parameters:

Parameter	Description
Mode	Specifies the form of check in. You can choose between: New - Creates 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 (see New mode). Update – Updates an existing version of the document in the current branch or creates a new version in the current branch if the document was checked out from a base branch of the current branch (see Update/Branch modes). Branch – Creates the first version of the document in the current branch (see Update/Branch modes). Integrate – Integrates changes in another branch of the version tree of the document, or check ins a document under another name (see Integrate mode).
Folder/Project	[available in New mode] Specifies the root node or a sub-folder where the document will be checked in into the repository. Click the Properties tool to the right of this field to open the property sheet of the folder. If you do not select a target folder, the document is checked in at the root of the browser. You should grant individual access permissions to this document.
Name	[not for project – available in Integrate mode] Specifies the name of the repository document with which to integrate. Click the Properties tool to open the property sheet of the document.
Version	[not for project – available in Integrate mode] Specifies the version of the repository document with which to check in.
Comment	Specifies a comment to help future users identify the purpose of the check in.
Freeze before check in	Freezes the previous versions of any modified objects in the repository, and creates a new version to accept the changes to be checked in.
Freeze after check in	Freezes all modified object versions after check in to ensure that no further changes can be made to them. Future changes to objects will be made to new versions.
Create baseline version	Creates a new version of all the objects in the entire model, whether or not they have been modified. This can be used as starting point for a new development step. This option is restricted to users with Full permission on selected document. A baseline version makes SQL queries faster because they do not have to deal with multiple object 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 check in problems when dealing with objects that are not properly handled in the repository. However, this may be fairly space consuming - the server will create large rollback logs, and use a large number of locks, and you might want to configure your server to allow such large transactions.
Unlock after check in	[locked documents only] Unlocks the document version after check in. If you do not select this option, the new or updated version is locked whereas the previous version is unlocked.
Save diagrams for PowerDesigner Portal	[not for resources] Prepares snapshots of the model diagrams that can be viewed in the PowerDesigner Portal (see Browsing the Repository Via the Web).

Project Documents

The Project Documents group box lists the model and file documents associated with the project, and lets you select them for check in with the project. Note that only project documents that are inside the projects are listed here. Documents that are outside the project and only attached to it are not listed and must be checked in separately.