Working with Named Releases of Repository Diagrams
Go Up to Working with Objects in the Repository
Named Releases are saved versions of a diagram, with a specified name. This version of the diagram can later be retrieved from the Repository for viewing or editing.
The following describe functions you may want to perform on named releases:
Contents
Set a Named Release
Saves the latest version of a diagram as a Named Release, with the specified name. This version of the diagram can later be retrieved from the Repository for viewing or editing.
- Log in to the Repository.
- Open the diagram that you want to set as a named release and then check it in to the Repository.
- Choose Repository > Releases > Set Named Release.
ER/Studio Data Architect adds the Named Release under the respective diagram. Named releases are indicated by a camera icon in the Explorer tree.
Notes
- When setting a Named Release, it is important to remember that uniqueness is enforced through the naming convention. You can determine a naming convention when setting a Named Release. If you want to associate the Diagram's file name with the Named Release, then you must enter the Diagram's file name as part of the name of the release.
- You can view a Named Release, but you cannot modify it. A special Repository operation, Rollback Diagram, lets you Check In a Named Release as the latest version of a diagram. Once the Rollback operation is completed, you can Check Out the diagram (or a portion of it) to modify it.
- When naming the Named Release, the name must be unique. We recommend using a naming convention that includes the name of the diagram in the release. The uniqueness is enforced at the Repository level, not the diagram level.
Get a Named Release or a Diagram
Using ER/Studio Repository, you can download named releases and diagrams from the Repository to a specified directory on the local machine. The Get From Repository operation lets you download diagrams, submodels, and named releases from the Repository. The Get From Repository dialog displays all diagrams and projects in the Repository and lets you expand each diagram node to show its submodels and named releases.
- To get a named release, choose Repository > Releases > Get Named Release.
- To get a diagram, choose Repository > Releases > Get Diagram.
- Complete the Get From Repository dialog as required.
The following describes options that are not self explanatory:
- Repository tree: Displays nodes for each Diagram in the Repository. Click the plus sign next to a node to expand and show all submodels and named releases. You can select individual objects to get from the Repository.
- General Information: Displays information about the repository, and the model or submodel selected. Information displayed includes Repository Version, Number of Models, Number of Nested Projects, and Users with checked out objects.
- Check Out Immediately: Available for submodels only. Immediately Checks Out to the local machine the items selected in the tree.
- Check Out Exclusively: Available for submodels only. If you have chosen Check Out Immediately, you can choose this option to immediately Check Out Exclusively to the local machine the items selected in the tree.
Notes
- You can make changes to objects you get, but changes do not reflect in the repository copy of the dm1 file until you check out and then check in the changes.
- You can view a named release, but, in general, you cannot modify it. A special repository operation, Rollback Diagram, lets you check in a named release as the latest version of a diagram. Once the Roll Back operation is completed, you can check out the diagram (or a portion of it) to modify it.
- If the local diagram has the same name as the diagram in the repository you want to get, you must rename the local copy of the diagram with a *.bak file extension. If you do not rename the local copy, you cannot complete the Get From Repository operation.
- If a file exists in the active file directory with the same name as the selected diagram or the same name as the diagram that the selected submodel belongs to, then there are several possible outcomes:
- If the local file is the same as the selected diagram or submodel, then ER/Studio Data Architect opens it and refreshes it with the latest Repository information.
- If the local file is from the same diagram, but contains a different submodel than the user selected (or the local file contains the entire diagram and the user selected a submodel, or vice versa), then ER/Studio Data Architect checks the local file for checked out objects. If any objects are checked out, ER/Studio Data Architect opens the local file instead of the selected diagram or submodel. This lets the user Check In their work. If no objects are checked out, the ER/Studio Data Architect deletes the local file and replaces it with the chosen diagram or submodel.
- If the local file is not a DM1 file, is a DM1 file from a previous version of ER/Studio Data Architect, is a DM1 file with a different diagram GUID, or is a DM1 file that has not yet been added to the repository, ER/Studio Data Architect renames the file with a BAK extension and ER/Studio Data Architect "Gets" the target diagram or submodel to the correct location.
- When you choose to get a named release, ER/Studio Data Architect gives you the option of specifying where to place the named release file. To see this option, you must select a named release in the tree (the UI is hidden and replaces the check out UI when the named release is selected).
Delete a Named Release
Lets you delete Named Releases of diagrams stored in the ER/Studio Repository. To delete a Named Release, you must already have Named Releases set in the server.
- Choose Repository > Releases > Delete Named Release.
- Click the Select a Named Release list and then select the target release.