Changes in Version 7.2
This section describes the changes to Axon in version 7.2.
Axon with Enterprise Data Catalog
Effective in version 7.2, the Axon and Enterprise Data Catalog integration includes the following changes:
- Onboarding Objects from Different Schemas in a Resource
- If two parents with the same name belong to two different schemas in Enterprise Data Catalog, Axon creates two different data sets based on the linked glossaries. For example, the EMP table is present in both FIN and HR schemas. The EMP table in the FIN schema is linked to the NAME glossary, and the EMP table in the HR schema is linked to the ID glossary. During automated onboarding, two data sets with the name EMP are created in Axon.
- Previously, if two parents with the same name belonged to two different schemas in Enterprise Data Catalog, Axon created a single data set based on the linked glossaries.
- Accept Onboarded Objects
- You can choose to accept onboarded objects when you run a data onboarding rule from a System object. The Accept Onboarded Objects field is moved from the Enterprise Data Catalog parameters on the Admin Panel to the System > Enterprise Catalog > Data Onboarding Rules page.
Previously, you could choose to accept onboarded objects from the Admin Panel.
For more information, see the Axon Data Governance 7.2 Administrator Guide and Axon Data Governance 7.2 User Guide.
Enhancements to Natural Language Processing (NLP) Capabilities for CLAIRE® Recommendations
Effective in version 7.2, when you enter a technical description for a standard data quality rule, CLAIRE® interprets the technical description and recommends a single rule or multiple rules. You can enter the technical description using flexible sentence constructions. CLAIRE® provides up to a maximum of four recommendations to generate a rule.
Previously, CLAIRE® recommended only a single rule based on the technical description that you entered. You could enter the technical description in a restricted format for CLAIRE® to recommend a rule.
For more information, see the Axon Data Governance 7.2 User Guide.
Local Data Quality Rules
Effective in version 7.2, local data quality rules include the following changes:
- •Axon automatically populates system name in the System Measured In field when you create a local data quality rule. You cannot modify the name of the system when you create or modify the local data quality rule. Even if the system belongs to the segment that is assigned to you, you cannot modify name of the system.
- •In the Measure Against field, you can select a system, data set, and attribute values based on the segments that are assigned to you. If a data set belongs to the segment and you are not assigned to that particular segment, you cannot view the Measured Against field.
For more information, see the Axon Data Governance 7.2 User Guide.
Label Change in Data Marketplace
Effective in version 7.2, the Inventory tab name is changed to Task in the Data Marketplace interface.
For more information, see the Axon Data Marketplace 7.2 User Guide.
People Objects
Effective in version 7.2, People objects include the following changes:
- •Only SuperAdmin users can update People objects through the Axon interface or bulk upload template. Previously, both Admin and SuperAdmin users could edit the details of the users.
- •A user with the Admin, SuperAdmin, or WebUser profile is restricted from modifying the details of users that are retrieved via LDAP directory or SSO.
For more information, see the Axon Data Governance 7.2 User Guide.
Label Changes in Axon Data Governance
Effective in version 7.2, you can see several label changes in the Axon interface and bulk upload templates. For example, System Name is changed to Short Name in the System object and role templates, and System Name is changed to System Short Name in the relationship templates, such as Capability X System and Business Area X System. When you create a data set or view the Data Set facet on Unison search, you can see that the System field is changed to System Short Name. When you link an Axon system to an Enterprise Data Catalog resource, you can see that the System Name field is changed to Short Name.
For more information on all the label changes in Axon 7.2, see the Informatica Knowledge Base article at
https://knowledge.informatica.com/s/article/LabelChanges-in-Axon-Data-Governance-72?language=en_US.
Date Filter
Effective in version 7.2, you can apply the date range filter in a single query on Unison search. You can select the Created Date filter and enter the From and To values in a single query.
Previously, you had to create two separate queries to select a single date range. You had to select the Created Date From and Created Date To values.
For more information, see the Axon Data Governance 7.2 User Guide.
Change Requests
Effective in version 7.2, the change request has the following changes:
- •The Status and Lifecycle fields are required for non-mandatory workflows.
- •You cannot edit a change request after the change request is completed or cancelled.
Fo more information, see the Axon Data Governance 7.2 User Guide.
Unison Search Results
Effective in version 7.2, if a Policy object is related to a Glossary object and the Glossary object is related to a System object via a Data Set or an Attribute object, Axon displays the related Glossary, Attribute, Data Set, and Systems objects if you perform a Unison search on the Policy object. This Unison search behavior applies to Policy, Process, and Project objects.
Previously, Axon displayed the related Glossary, Attribute, and Data Set objects if you performed a Unison search on a Policy object.
For more information, see the Axon Data Governance 7.2 User Guide.
Mailer Transport
Effective in version 7.2, the Mailer Transport field appears as a dropdown list instead of a text field.
For more information, see the Axon Data Governance 7.2 Administrator Guide.