Checking Documents into the Repository

You check documents into the repository to share them with others. You must have at least the Submit permission on a document (or on one of its packages) to be able to check it into a change list for approval or at least the Write permission to make changes directly to the repository version.

  1. In the Local tab of the Browser, select the documents to check in, then right-click and select Check In to open the:
  2. Select whether to check into a change list (see Change Lists). You can choose from:
    • <None> - [if you have Write permission on the target folder] Allows you to check the item in directly without review.
    • <New change list> - To create a new change list to contain the checked in item.
    • Change list_xxxx - To add the item to an existing draft change list. Click the Properties tool to the right of this field to access the property sheet of the change list.
      Note: If you are checking in a new version of an item that is already contained in a draft change list, then this field is read-only.
  3. Select any other appropriate parameters (see Check-In Parameters), and click OK to check in the document.
    If you check into a change list, you can add other documents to it as necessary through other check ins before submitting it (see Creating, Building, and Submitting a Change List). Once the change list has been approved by the reviewers, your changes are integrated into the official repository versions of the models and made available to other users. If an administrator has connected the repository to an SMTP server (see Connecting to an SMTP Server for Notifications) you will receive an email at the moment of submission of your change list and when it is approved, rejected, or returned to you for further revision.
  4. If you are checking in a document that is already stored in the repository, the Merge Changes to Repository Document dialog (see Resolving Conflicts During Check In) may open to let you review the differences between your local document and the version in the repository. When you are satisfied, click OK to complete the check in.
    Note: If you have changed the target (DBMS, OO language, etc) of the model outside of the target family (such as moving from Oracle 11g to Sybase ASE 15.7), you will not be able to create a new version of the existing repository document and will need to save the model as a new document in the repository.