Release Guide > Part V: Version 9.6.1 > New Features, Changes, and Release Tasks (9.6.1 HotFix 3) > Changes (9.6.1 HotFix 3)
  

Changes (9.6.1 HotFix 3)

This section describes changes in version 9.6.1 HotFix 3.

Business Glossary

This section describes changes to Business Glossary in version 9.6.1 HotFix 3.

Business Glossary Export File

Effective in version 9.6.1 HotFix 3, the order of worksheets in the Business Glossary export file is rearranged. The worksheets that are not recommended to be altered in Microsoft Excel are hidden. The first worksheet is a home page and it provides a brief description of other worksheets in the export file.
Previously, the export file did not have hidden worksheets and a home page.

Business Glossary Security

Effective in version 9.6.1 HotFix 3, a user who is assigned the Manage Glossaries privilege in the Analyst tool for a particular glossary cannot perform user and role management for any other glossary.
Previously, a user who was assigned the Manage Glossaries privilege in the Analyst tool could modify the permissions and privileges of a user for any glossary.

Glossary Import

Effective in version 9.6.1 HotFix 3, when you import a glossary that is not present in Business Glossary, the Analyst tool creates the glossary during import. When you import a glossary, the Analyst tool automatically populates the custom properties which are present in the glossary with values from the export file. The Analyst tool also attaches the custom properties to the relevant templates, even if the custom properties were not attached to any template before the import process.
Previously, if wanted to import a glossary that was not present in Business Glossary, you first needed to create the glossary in the Analyst tool before importing the glossary contents from the export file. The Analyst tool did not populate the custom properties with information from the export file, when they were not attached to any template.

Synonyms

Effective in version 9.6.1 HotFix 3, synonyms in business terms have the following changed behavior:
Previously, you could not remove or modify the retirement date. You could only use the date picker to set the date. You could not view the date of creation in the business term.

Informatica Transformations

This section describes the changes to the Informatica transformations in version 9.6.1HotFix 3.

Address Validator Transformation

This section describes the changes to the Address Validator transformation.

Data Processor Transformation

This section describes the changes to the Data Processor transformation.

XmlToXlsx with Template

The XmlToXlsx document processor converts XML documents to Microsoft Excel .xlsx format. Effective in version 9.6.1 HotFix 3, the XmlToXlsx document processor can optionally use an .xlsx template with the XML document to generate the .xlsx document.
Previously, you could generate an .xlsx document based on an XML document.

Metadata Manager

This section describes changes to Metadata Manager in version 9.6.1 HotFix 3.

Business Glossary Resources

Effective in version 9.6.1 HotFix 3, Business Glossary resources have behavior changes.
Business Glossary resources have the following behavior changes:
Privileges required to load Business Glossary resources
Effective in 9.6.1 HotFix 3, to load Business Glossary resources, you need the Load Resource, Manage Resource, and View Model privileges.
Previously, to load Business Glossary resources, you needed the Load Resource and Manage Models privileges for the Metadata Manager Service.
Migrating related catalog objects after upgrade
Effective in version 9.6.1 HotFix 3, do not run the mmcmd migrateBGLinks command after you upgrade a business glossary from version 9.5.x. The migrateBGLinks command restores related catalog objects for upgraded business glossaries. The command now runs automatically the first time that you load a Business Glossary resource after upgrade.
Previously, you had to run the migrateBGLinks command as the last step in the upgrade process for business glossaries.
Related catalog objects for categories
Effective in version 9.6.1 HotFix 3, you cannot create related catalog objects for categories. You can still create related catalog objects for business terms.
Previously, you could relate categories to other categories or to business glossaries in Metadata Manager, but you could not relate categories to other metadata objects. If you did create category to category or category to glossary relationships in Metadata Manager, Metadata Manager did not update these relationships in the Analyst tool business glossary.
To create term to term, term to category, category to term, or category to category relationships, use the Analyst tool.
Property names that contain special characters
Effective in 9.6.1 HotFix 3, Metadata Manager can load Business Glossary resources that contain custom properties with special characters in the name. However, Metadata Manager does not extract custom properties that contain special characters in the name.
Specifically, Metadata Manager does not extract custom properties with names that contain any of the following special characters:
~ ' & * ( ) [ ] | \ : ; " ' < > , ? /
Previously, if you tried to load a Business Glossary resource that contained custom properties with any of these characters in the name, the load failed.

Microsoft SQL Server Integration Services Resources

Effective in version 9.6.1 HotFix 3, the property that controls how Metadata Manager displays lineage for Script components that are used as transformations is renamed to Hide transformation scripts.
Previously, the property was called Transformation scripts.

SAP PowerDesigner Resources

Effective in version 9.6.1 HotFix 3, Sybase PowerDesigner resources are called SAP PowerDesigner resources.

Permissions

Effective in version 9.6.1 HotFix 3, permissions control which resources that users can access on the Load tab as well as the Browse tab. To perform an action on a resource, a user needs both the appropriate privilege and the appropriate permission on the resource.
For example, to view a resource on the Load tab, a user needs the View Resource privilege and read permission on the resource. To load a resource, a user needs the Load Resource privilege and write permission on the resource. To edit a resource, a user needs the Manage Resource privilege and write permission on the resource.
Because of this change, the resources that a user sees on the Load tab match the resources that the user sees on the Browse tab. The user no longer sees all resources on the Load tab unless the user has at least read privilege on all resources.
Previously, permissions determined which resources and metadata objects that users could access on the Browse tab, but they did not affect the Load tab. Permissions for the Browse tab are not changed.

Metadata Manager Reports

Effective in version 9.6.1 HotFix 3, when you restart the domain, you no longer have to recycle the Metadata Manager Service to enable the View Reports button. If the domain contains a Reporting and Dashboards Service, the View Reports button is always enabled.
Previously, when you restarted the domain, you had to recycle the Metadata Manager Service to enable the View Reports button.

Security

This section describes changes to security in version 9.6.1 HotFix 3.
Effective in version 9.6.1 HotFix 3, Informatica dropped support for SSL keys that use fewer than 512 bits if they use RSA encryption. This change affects secure communication within the Informatica domain and secure connections to web application services.
If your SSL keys are affected by this change, you must generate new RSA encryption based SSL keys with more than 512 bits or use an alternative encryption algorithm. Then, use the new keys to create the files required for secure communication within the domain or for secure connections to web application services. For more information about the files required for secure communication within the Informatica domain or secure connections, see the Informatica Security Guide.
Previously, Informatica supported RSA encryption based SSL keys that use fewer than 512 bits.