Check in Parameters

Local Document

The Local Document group box contains the following parameters:

Parameter	Description
Workspace or File	[not for project] Select a radio button 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. Depending on whether you have selected Workspace or File, this will be a: Model name - click the Properties tool to open its property sheet File name and path - click the Browse tool 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 available
Check out after check in	[models and resources only] Updates the local version after check in by checking out the repository version to ensure that you have the most up-to-date version where other users may be working concurrently.
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 type of check in. You can choose between: New - [always available] The document is not yet in the repository, or not yet in the current branch (see Branching Version Trees), or you want to check it into a new location in the current branch. Update/Branch – These modes are mutually exclusive and one is always selected by default depending on whether the document already exists in the current branch or one of its base branches. The Project, Folder, Name, and Version fields are read-only: Update - Updates 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. Branch - Creates the first version of the document in the current branch. Integrate – [always available] You want to merge the document into another version in a parallel branch or into a different document. Note: Each check in is processed as one transaction. If you check in large models using the New mode, 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. The other modes use much smaller transactions. For example of the use of check in modes, see Checking in a Document Using the Update, Branch, and Integrate Modes)
Folder/Project	[read-only except in New mode] Specifies the location where the document will be checked in. Click the Properties tool to open the property sheet of the folder. If you do not specify 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 – read-only except in Integrate mode] Specifies the name of the document to apply your changes to. Click the Properties tool to open the property sheet of the document.
Version	[not for project – read-only except in Integrate mode] Specifies the version of the document to apply your changes to.
Comment	Specifies a comment to describe 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 (see Freezing Document Versions).
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 (see Freezing Document Versions).
Create baseline version	Creates a completely new version of the model, instead of simply versioning the objects that have changed. This option is only available if you have `Full` permission on the document. The Merge Changes to Repository Document dialog will not open. Baseline versions may be quicker to check in and out, but they require considerably more disk space than standard versions. The server will create large rollback logs, and use a large number of locks, and might need to be configured to allow large transactions. Occasionally the repository is unable to process a standard version, and in this situation you should try to create a baseline version. This can be used as starting point for a new development step.
Unlock after check in	[locked documents only] Unlocks the document version after check in (see Locking Document Versions).
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 project are listed here. Documents that are outside the project and only attached to it must be checked in separately.