ER/Studio - Embarcadero Technologies Product Documentation
ER/Studio - Embarcadero Technologies Product Documentation ER/Studio - Embarcadero Technologies Product Documentation
WORKING WITH THE REPOSITORY > WORKING WITH OBJECTS IN THE REPOSITORY • 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 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 checks the local file for checked out objects. If any objects are checked out, ER/Studio 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 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, 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 renames the file with a BAK extension and ER/Studio “Gets” the target diagram or submodel to the correct location. • When you choose to get a named release, ER/Studio 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. 1 Click Repository > Releases > Delete Named Release. 2 Click the Select a Named Release list and then select the target release. Branching and Merging Diagrams Branches are typically needed for testing or development purposes and then, once stabilized, merged into the currently deployed model. You can branch and sub-branch as often as you want. 1 Open the target diagram for branching or merging 2 Click Repository > Diagrams > Branch/Merge Diagram. 3 To create a branch of the active diagram, from the Branch Tree, select the diagram to be branched and then click the Branch button. To create a branch of the active diagram, from the Branch Tree, select the diagram or branch of the diagram to be merged and then click Merge. The following describes options that may not be self-explanatory. Display deleted diagrams: Select this option to view all branches of the diagram, including those that were previously deleted. Deleted diagrams are unavailable and cannot be selected to use with the Branch or Merge functions. EMBARCADERO TECHNOLOGIES > ER/STUDIO® 8.0.3 USER GUIDE 290
WORKING WITH THE REPOSITORY > WORKING WITH OBJECTS IN THE REPOSITORY Notes • It is good engineering practice to stick with a single enumeration convention, be it alphanumeric or some other series, and to use descriptive names. • You can select whether the *.dm1 file name or the diagram name is displayed by changing the display option: Click Repository > Options > General and then change the Diagram Name Display Format. Rolling Back a Diagram to a Previous Version Use the Rollback function to replace the most current version of a named release in the repository to a previous version of the diagram. The Rollback Diagram operation is particularly useful when you want to return to a previous version of your diagram because a later version has changes you no longer need or want to use. 1 Login in to the Repository and get a Named Release. 2 Review the Diagram to ensure you want to rollback to a previous release. 3 Click Repository > Diagrams > Rollback Diagram. Notes • When the rollback operation is completed, you can check out the diagram (or a portion of it) to modify it. • We recommend that you review the diagram to be sure that you want to rollback to this version. Deleting a Diagram from the Repository NOTE: Deleting a diagram is a destructive action. Before deleting a diagram, notify other users who can be currently accessing it. 1 Log in to the repository. 2 Click Repository > Diagrams > Delete Diagram. 3 In the Select a Diagram to Delete dialog, select the diagram to delete. 4 Select the Leave Diagram Data behind and marked as Deleted check box. NOTE: Although not required, you should use this option because it will prevent total loss of the diagram. With this option selected, you can later retrieve the diagram if necessary. 5 Click OK. Notes • When you delete a Diagram from the Repository, the local copy of the Diagram is also deleted. If you want to save your local copy of the Diagram, you must rename the *.DM1 file. • When deleting a diagram, ER/Studio leaves diagram data behind and marks it as deleted. If deleted, data is still present in the repository but visible only when querying the Repository directly, not through ER/Studio client. EMBARCADERO TECHNOLOGIES > ER/STUDIO® 8.0.3 USER GUIDE 291
- Page 239 and 240: USING ER/STUDIO > WORKING WITH THE
- Page 241 and 242: USING ER/STUDIO > DOCUMENTING DATA
- Page 243 and 244: USING ER/STUDIO > DOCUMENTING DATA
- Page 245 and 246: USING ER/STUDIO > DOCUMENTING DATA
- Page 247 and 248: USING ER/STUDIO > DOCUMENTING DATA
- Page 249 and 250: USING ER/STUDIO > SAVING AND USING
- Page 251 and 252: USING ER/STUDIO > GENERATING RTF AN
- Page 253 and 254: USING ER/STUDIO > EXPORTING THE DAT
- Page 255 and 256: USING ER/STUDIO > EXPORTING THE DAT
- Page 257 and 258: USING ER/STUDIO > EXPORTING THE DAT
- Page 259 and 260: USING ER/STUDIO > EXPORTING THE DAT
- Page 261 and 262: USING ER/STUDIO > EXPORTING THE DAT
- Page 263 and 264: USING ER/STUDIO > EXPORTING THE DAT
- Page 265 and 266: USING ER/STUDIO > EXPORTING THE DAT
- Page 267 and 268: USING ER/STUDIO > EXPORTING THE DAT
- Page 269 and 270: USING ER/STUDIO > EXPORTING THE DAT
- Page 271 and 272: USING ER/STUDIO > EXPORTING THE DAT
- Page 273 and 274: USING ER/STUDIO > EXPORTING THE DAT
- Page 275 and 276: USING ER/STUDIO > EXPORTING AN IMAG
- Page 277 and 278: WORKING WITH THE REPOSITORY > WORKI
- Page 279 and 280: WORKING WITH THE REPOSITORY > WORKI
- Page 281 and 282: WORKING WITH THE REPOSITORY > WORKI
- Page 283 and 284: WORKING WITH THE REPOSITORY > WORKI
- Page 285 and 286: WORKING WITH THE REPOSITORY > WORKI
- Page 287 and 288: WORKING WITH THE REPOSITORY > WORKI
- Page 289: WORKING WITH THE REPOSITORY > WORKI
- Page 293 and 294: WORKING WITH THE REPOSITORY > WORKI
- Page 295 and 296: WORKING WITH THE REPOSITORY > WORKI
- Page 297 and 298: WORKING WITH THE REPOSITORY > CANCE
- Page 299 and 300: AUTOMATING ER/STUDIO > Related Topi
- Page 301 and 302: AUTOMATING ER/STUDIO > Object Model
- Page 303 and 304: AUTOMATING ER/STUDIO > Macros which
- Page 305 and 306: AUTOMATING ER/STUDIO > Meta Data Ma
- Page 307 and 308: AUTOMATING ER/STUDIO > • Definiti
- Page 309 and 310: AUTOMATING ER/STUDIO > Access ER/St
- Page 311 and 312: AUTOMATING ER/STUDIO > You can cust
- Page 313 and 314: AUTOMATING ER/STUDIO > The table be
- Page 315 and 316: AUTOMATING ER/STUDIO > Click the ?
- Page 317 and 318: Administrator’s Reference This se
- Page 319 and 320: ADMINISTRATOR’S REFERENCE > CONNE
- Page 321 and 322: ADMINISTRATOR’S REFERENCE > UNDER
- Page 323 and 324: ADMINISTRATOR’S REFERENCE > MANAG
- Page 325 and 326: ADMINISTRATOR’S REFERENCE > MANAG
- Page 327 and 328: ADMINISTRATOR’S REFERENCE > MANAG
- Page 329 and 330: ADMINISTRATOR’S REFERENCE > ESTAB
- Page 331 and 332: ADMINISTRATOR’S REFERENCE > ESTAB
- Page 333 and 334: ADMINISTRATOR’S REFERENCE > ESTAB
- Page 335 and 336: ADMINISTRATOR’S REFERENCE > ESTAB
- Page 337 and 338: Tutorials The tutorials are intende
- Page 339 and 340: TUTORIALS > GETTING STARTED WITH ER
WORKING WITH THE REPOSITORY > WORKING WITH OBJECTS IN THE REPOSITORY<br />
• You can view a named release, but, in general, you cannot modify it. A special repository operation, Rollback<br />
Diagram, lets you check in a named release as the latest version of a diagram. Once the Roll Back operation is<br />
completed, you can check out the diagram (or a portion of it) to modify it.<br />
• If the local diagram has the same name as the diagram in the repository you want to get, you must rename the<br />
local copy of the diagram with a *.bak file extension. If you do not rename the local copy, you cannot complete<br />
the Get From Repository operation.<br />
• If a file exists in the active file directory with the same name as the selected diagram or the same name as the<br />
diagram that the selected submodel belongs to, then there are several possible outcomes:<br />
• If the local file is the same as the selected diagram or submodel, then <strong>ER</strong>/<strong>Studio</strong> opens it and refreshes it with<br />
the latest Repository information.<br />
• If the local file is from the same diagram, but contains a different submodel than the user selected (or the local<br />
file contains the entire diagram and the user selected a submodel, or vice versa), then <strong>ER</strong>/<strong>Studio</strong> checks the<br />
local file for checked out objects. If any objects are checked out, <strong>ER</strong>/<strong>Studio</strong> opens the local file instead of the<br />
selected diagram or submodel. This lets the user Check In their work. If no objects are checked out, the<br />
<strong>ER</strong>/<strong>Studio</strong> deletes the local file and replaces it with the chosen diagram or submodel.<br />
• If the local file is not a DM1 file, is a DM1 file from a previous version of <strong>ER</strong>/<strong>Studio</strong>, is a DM1 file with a different<br />
diagram GUID, or is a DM1 file that has not yet been added to the repository, <strong>ER</strong>/<strong>Studio</strong> renames the file with<br />
a BAK extension and <strong>ER</strong>/<strong>Studio</strong> “Gets” the target diagram or submodel to the correct location.<br />
• When you choose to get a named release, <strong>ER</strong>/<strong>Studio</strong> gives you the option of specifying where to place the<br />
named release file. To see this option, you must select a named release in the tree (the UI is hidden and replaces<br />
the check out UI when the named release is selected).<br />
Delete a Named Release<br />
Lets you delete Named Releases of diagrams stored in the <strong>ER</strong>/<strong>Studio</strong> Repository. To delete a Named Release, you<br />
must already have Named Releases set in the server.<br />
1 Click Repository > Releases > Delete Named Release.<br />
2 Click the Select a Named Release list and then select the target release.<br />
Branching and Merging Diagrams<br />
Branches are typically needed for testing or development purposes and then, once stabilized, merged into the<br />
currently deployed model. You can branch and sub-branch as often as you want.<br />
1 Open the target diagram for branching or merging<br />
2 Click Repository > Diagrams > Branch/Merge Diagram.<br />
3 To create a branch of the active diagram, from the Branch Tree, select the diagram to be branched and then<br />
click the Branch button.<br />
To create a branch of the active diagram, from the Branch Tree, select the diagram or branch of the diagram to<br />
be merged and then click Merge.<br />
The following describes options that may not be self-explanatory.<br />
Display deleted diagrams: Select this option to view all branches of the diagram, including those that were<br />
previously deleted. Deleted diagrams are unavailable and cannot be selected to use with the Branch or Merge<br />
functions.<br />
EMBARCAD<strong>ER</strong>O TECHNOLOGIES > <strong>ER</strong>/STUDIO® 8.0.3 US<strong>ER</strong> GUIDE 290