ER/Studio Data Architect 16.5 release notes updated November 7, 2016.
Release 16.5 features summary:
Updated Data Modeling and Lineage
Universal mappings enhancements
- ER/Studio Enterprise Team Edition 16.5 expands universal mapping to add and view definitions, attachment bindings, and notes related to universal mappings. Icons adjacent to mappings that contain a definition, note, or attachment bindings let the user know that additional information is available. In addition, user-defined mappings also now have the ability to include a note. For more information about universal mappings, see Working with Universal Mappings.
Improved relationship diagramming
- Viewing data models can occasionally become cluttered with the number of relationships associated with the model. The Data Model View in ER/Studio Data Architect 16.5 introduces a toggle option that allows you to hide or unhide one, more, or all relationships in a submodel. To hide a relationship, simply select and right-click the item(s) you want to hide or unhide, and then select either Hide Relationship or Show All Hidden Relationships from the available menu. Note that when publishing models to Team Server, all hidden relationships remain hidden in the graphical display. For more information about managing relationships, see Creating and Editing Relationships.
Improved glossary integration
- ER/Studio Data Architect XE7 introduced the ability to automatically link your Team Server glossaries directly into the ER/Studio interface. ER/Studio Enterprise Team Edition 16.5 continues to improve this feature by allowing association of specific models or sub-models in a .dm1 file and repository to be associated with a specific glossary. That glossary then can provide the scope when trying to detect and link terms to the model objects. If a glossary term is used in the Name, Definition, or Notes of a model object, it is highlighted to identify that you have a definition in your Team Server Glossary. Holding your mouse cursor over the highlighted term pops up the short definition while control-clicking on the term will navigate to that term in the Team Server Glossary. For more information about glossaries, see Glossary Integration or the ER/Studio Team Server online help section about Working with Glossaries.
Database Platform Support
- ER/Studio Data Architect 16.5 now includes database platform support for IBM DB2 for z/OS v11.x and SQL Server 2016 (does not include support for SQL Server 2016 JSON capabilities). For more information about supported platforms, see Supported Database Platforms.
- ER/Studio Enterprise Team edition includes additional features to expand the support for Agile change management. Users now can associate tasks from third-party tools, such as Atlassian JIRA, to specific projects available within the Repository Project Center. Similar support also is expanded in Team Server, where you can add, change, and delete the same tasks. JIRA is the only issue- and project-tracking tool supported in this release. For more information about using this feature, see Change Records and Working with Repository Projects.
Improved User Experience through Updated Interface and Features
- This release begins a rollout of rebranding this product from Embarcadero to IDERA. Note that these changes include a new license agreement, installation and data directories, icons, file names, registry settings, and more. For more information about IDERA and IDERA products, see https://www.idera.com/.
Added pinned file ability in the Welcome tab and File menu
- ER/Studio Data Architect 16.5 includes new features on the Welcome tab that appears when you log in to the product. This area displays links to helpful tutorials and resources as well as Start links to begin some more commonly-used tasks, such as creating a new model and open an existing diagram. New for this release are an expanded Recent Files list and the option to "pin" selected items to a Pinned Files list. These same features also area added to the File menu within Data Architect. Changes in either area are automatically reflected in the other area. Note that you are limited to 15 pinned files and that you can removed a file from the pinned list by clicking the delete (x) icon.
Supports rich text functionality on entry fields
- All fields where a user can type names, definitions, notes, etc. now include a spell check, allow some rich text functions such as bold and underlined text, and support embedded hyperlinks. In larger fields, a text wrap feature also was implemented. Available rich text options include:
- Text font, color, and size
- Bold, italics, and underline
- Format and alignment options including bullets
- Hyperlink capability
Added the ability to inherit relationship color from parent entity
- The Colors & Fonts dialog now includes the Inherit from parent entity foreground checkbox that allows users to set whether you want the outline of an entity to be the same color as its parent entities. If you select a relationship and change its color, the manual change overrides the color inherited from the parent. Changes made in a child entity do not affect the color of the parent. For more information about setting diagrams colors, see Setting Default Diagram Colors and Fonts. This option is enabled only for the following object types when selected from the drop-down list available in the Colors & Fonts dialog:
- Relationship object type. Relationship color is the same as the parent entity foreground (border.)
- Inherited Primary Keys object type. Primary font color is the same as parent entity foreground (border).
- Inherited Non-Keys. Foreign key color is the same as parent entity foreground (border).
Implemented unique tokens to identify repository checkout records
- In this release of ER/Studio Data Architect, checkouts now include a unique identifier or token to easily resolve identification issues when attempting to check in to the Repository. Previously, checkouts included the host machine name as part of the identifier in the checkout record. This process caused issues in virtualized environments when the host names did not match upon reconciliation at check in, perhaps because the user disconnected from the repository before checking in the work.
Improved repository security for new users and assigned roles
- This release of ER/Studio Repository features the following security enhancements to the Security Center:
- When a new user is added, the user has the ability to log into the repository but has NO ACCESS to projects. An administrator must assign a role with the proper access to this user account.
- Role assignment is inherited by all objects under the node for which the role is specified. For example, if you grant UserA access ProjectX, then UserA can access all elements under ProjectX. But if you want to restrict UserA's access to only a single element within ProjectX, such as Model1, you can grant access to Model1 while also granting a NO ACCESS role to UserA at the ProjectX level. The lower level access to Model1 has a higher priority than the ProjectX NO ACCESS role.
- For more information about managing repository security, see Establishing Security for the Repository.